TIDY - proposal - add comment to Else, EndIf , EndSelect, EndIf , WEnd

[mLipok]

#include <MsgBoxConstants.au3>
Func _First_example()
    Local $sString = ""
    If $sString > 0 Then
    ElseIf $sString < 0 Then
        MsgBox($MB_SYSTEMMODAL, "", "Value is positive.")
        MsgBox($MB_SYSTEMMODAL, "", "Value is negative.")
    Else
        If StringIsXDigit($sString) Then
            MsgBox($MB_SYSTEMMODAL, "", "Value might be hexadecimal!")
        Else
            MsgBox($MB_SYSTEMMODAL, "", "Value is a string.")
        EndIf
;~      EndIf ; why aftere folding this EndIf (I mean from line #13) is not visible
    EndIf
;~  EndIf ; why aftere folding this EndIf (I mean from line #15) is not visible
EndFunc   ;==>_First_example

In fact, I often use this functionality "code folding" but not always ending "EndIf" was for me a "distracting" - Please see my comments in the example.

EDIT:

This phrase better give my thoughts in this way.

In fact, I often use this functionality "code folding", but always, no ending "EndIf" was for me a "distracting"

EDIT2:

I'll write a few similar thoughts about, "code folding" but it will take a while, and besides, I preferred my every think, describe the individual.

Edited August 19, 2013 by mlipok

[Chimaera]

I comment my stuff but thats because i have a bad memory so at least i can tell whats been done or why.

But i cant say im in favour of an auto comment especially if it overwrites my comments.

The only way that would make any sense is some kinda of auto numbering but i have no idea how you would implement it see below

[1] If $sString > 0 Then

   [1] ElseIf $sString < 0 Then

        MsgBox($MB_SYSTEMMODAL, "", "Value is positive.")

        MsgBox($MB_SYSTEMMODAL, "", "Value is negative.")

   [1] Else

       [2] If StringIsXDigit($sString) Then

            MsgBox($MB_SYSTEMMODAL, "", "Value might be hexadecimal!")

       [2] Else

            MsgBox($MB_SYSTEMMODAL, "", "Value is a string.")

       [2] EndIf

   [1] EndIf

[FireFox]

I agree, but I do not know whether it would be feasible.

Of course it is

[mLipok]

 

I comment my stuff but thats because i have a bad memory so at least i can tell whats been done or why.

But i cant say im in favour of an auto comment especially if it overwrites my comments.

The only way that would make any sense is some kinda of auto numbering but i have no idea how you would implement it see below

[1] If $sString > 0 Then

   [1] ElseIf $sString < 0 Then

        MsgBox($MB_SYSTEMMODAL, "", "Value is positive.")

        MsgBox($MB_SYSTEMMODAL, "", "Value is negative.")

   [1] Else

       [2] If StringIsXDigit($sString) Then

            MsgBox($MB_SYSTEMMODAL, "", "Value might be hexadecimal!")

       [2] Else

            MsgBox($MB_SYSTEMMODAL, "", "Value is a string.")

       [2] EndIf

   [1] EndIf

I think my next thoughts are partly coincide with yours.

[mLipok]

I see in SciTE: [MENU]View/Toogle all folds

The result of this function is known to everyone (as I suppose)

 

but to compare him to introduce "SCITE_Folding_1.jpg"

 

I hope that the result will be more helpful would have been like "SCITE_Folding_2.jpg"

 

Please look to the accompanying examples

 

ps.

"SCITE_Folding_2.jpg" is the result of the "mspaint"

 

 

 

[Jos]

One thing could be useful: retain folds (natives and also for #region) upon editor exit.

The folding is save when the session is closed (SciTE exit) and then opened again when session.folds=1 is set, which is the default.

Jos

[Jos]

 

I see in SciTE: [MENU]View/Toogle all folds

Have you seen this explanation in the SciTE documentation on how this works? It is part of the helpfile I provide with the full installer.

 

Folding

SciTE supports folding for many languages (see the list of languages understood by SciTE for more information.) Fold points are based upon indentation for Python and on counting braces for the other languages.

The fold point markers (in the fold margin) can be clicked to expand and contract folds. Normal clicking does not alter the fold state of child fold points; naturally the children are hidden when the parent fold is contracted, but when the parent is expanded again, each child is still folded or not, as before.

Ctrl+Click on a fold point toggles it and performs the same operation on all children.

Shift+Click on a fold point does not toggle that fold, it expands all the child folds.

Ctrl+Shift+Click in the fold margin expands or contracts all the top level folds. "Toggle all folds" in the View menu does the same; it toggles only top-level folds.

Tip: To open a large code block with all its children folded, fold it with Ctrl+Click, then open it with a normal click. Then on opening a child fold, you will see that the grandchild folds are still closed; if you want those 'grandchild' folds open, Shift+Click the child fold.

Edited August 19, 2013 by Jos

[mLipok]

Have you seen this explanation in the SciTE documentation on how this works? It is part of the helpfile I provide with the full installer.

 

 

Tip: To open a large code block with all its children folded, fold it with Ctrl+Click, then open it with a normal click. Then on opening a child fold, you will see that the grandchild folds are still closed; if you want those 'grandchild' folds open, Shift+Click the child fold.

 

This is just great.

 

I did not know about it.

The bait but honestly who else knew about it?

[FireFox]

The folding is save when the session is closed (SciTE exit) and then opened again when session.folds=1 is set, which is the default.

 

Jos

Yes that's why I would like it to be saved even SciTE is exited.

[Jos]

Yes that's why I would like it to be saved even SciTE is exited.

You are confusing me.... Are you saying that when you close SciTE and then start it again, the Fold state is not restored?

[FireFox]

No, it's not restored.

Should it work with the #regions too?

[Jos]

No, it's not restored.

Should it work with the #regions too?

Of course, SciTE is unaware what the fold is for when saving it to SciTE.session at closing of SciTE.

So in your case no folds are saved at all?

Jos

[FireFox]

So in your case no folds are saved at all?

No, even if I don't exit SciTE (just tested).

[Jos]

The only way the folds and bookmarks are saved in SciTE.session is when you Close SciTE, not individual files.

Do you have any modifications made to "save.session=1" in any of your properties files?

Check SciTE.session after closing SciTE to see what it contains.

Jos

[FireFox]

I never touched the properties on both computers, my options save.session and session.folds are set to 1.

[mLipok]

The only way the folds and bookmarks are saved in SciTE.session is when you Close SciTE, not individual files.

Do you have any modifications made to "save.session=1" in any of your properties files?

Check SciTE.session after closing SciTE to see what it contains.

Jos

 

Jos in my SciTE.Session there is no save.sesion properties

 

 

# SciTE session file

position.left=516

position.top=155

position.width=1015

position.height=487

position.maximize=1

 

mru.1.path=L:TOOLsMacrotest TIDY.au3

mru.2.path=L:TOOLsMacroTEST SciTE Folding.au3

 

buffer.1.path=L:TOOLsMacroTEST SciTE Folding.au3

buffer.1.position=1

buffer.1.current=1

buffer.1.folds=2 

 

 

 

 

and I have the same problem as FireFox say.

Edited August 19, 2013 by mlipok

[Jos]

What version of SciTE are you testing with?

[FireFox]

3.2.0

[mLipok]

Unfortunately I can not say which version of the problem occurred.

This is because in the meantime I could upgrade the latest BETA version everything I could (SciTE.exe, SciLexer.dll, Tidy.exe, Obfuscator.exe, AutoIt3Wrapper.exe) , and now this functionality is already working properly.

 

btw.

Can you add to TIDY and Au3Check option to report the version of SciTE, in the Console window

And the second question: whether AU3Check is somehow updated to some BETA because the page:

http://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/

 

It does not contain the update.

[Jos]

3.2.0

Try the current Beta as many changes have been made since then.

 

Unfortunately I can not say which version of the problem occurred.

I am only talking about SciTE now