150 replies to this topic

[Jos]

Ah hah, I thought you were being serious about wanting a snippet.

I was till I found out in your second post you were using this new function... sorry about that .

[Jos]

Uploaded a new version of SciTE.exe & scilexer.dll 3.02. This set contains the same changes as the latest Beta SciTE 2.28:

I have update the Current available Beta SciTE v2.28, SciLexer and SciTEGlobal.properties to enable the fold.highlight and us RED for that.
Also changed the closing fold level to be consistent meaning it will fold to a single line and not showing the last statement for any fold block.
I am considering to add an extra option to support the old folding in case there are many that would like to see that option.
I have been doing a lot of changes to the Folding logic including folding inside comments so let me know when there are issue.
Remark: The folding in commentblock doesn't support all folding since a part of the logic is basic on the lexer keyword detection which doesn't work in commentblock as that is all marked a comment.

Edited by Jos, 22 January 2012 - 02:55 PM.

[matwachich]

I Really think that the only that's missing from Scite is a project manager!
I use Programmer's Notepad ONLY for it's good Project Manager.

Would it be possible to add a project manager, just like SciteJump or Function Popup???

Thanks

[ProgAndy]

I Really think that the only that's missing from Scite is a project manager!
I use Programmer's Notepad ONLY for it's good Project Manager.

Would it be possible to add a project manager, just like SciteJump or Function Popup???

Thanks

Write and maintain a stable Project Manager and it will be added I think

[Jos]

Finally about the inline errors. Those are implemented via something called Annotations. It may be something that can be done via Lua. Also I've discovered that there is a menu command (Tools -> Next Message) that will automatically jump to a message (moves the cursor, boo) and show the inline errors (yay). It may be possible to do something like wrap invoking Au3Check in Lua so that we can do fun things like automatically show the inline errors after running Au3Check as well as automatically clearing orphaned errors by just running Au3Check cleanly. It may also be possible to save/restore the current position so it's a little less annoying.

This can be done via LUA by using OnUpdateUI(). It will require some proper testing to ensure it won't be constantly lexing the output shown in the Outputpane.
Just for having a play with this I started to add some Annotations logic in AutoIt3Wrapper, were I capture the au3check output.
I am not so sure this is really going to improve things but got some basics working.

Edited by Jos, 24 January 2012 - 08:01 PM.

[UEZ]

If I type IfThen in SciTE then it will become red and I cannot be modified only delete any character.


Br,
UEZ

[Jos]

If I type IfThen in SciTE then it will become red and I cannot be modified only delete any character.

Type IfThen and hit Space ..... the abbrev magic should happen.

[UEZ]

Ahhhhh, that's really magic.

THANKS!

Br,
UEZ

Edited by UEZ, 24 January 2012 - 08:25 PM.

[Jos]

Ahhhhh, that's really magic.

There is a real nice long list of implemented Abbreviations which can be found in the SciTE4AutoIt3 helpfile.
It is one of those features that probably many aren't aware of its existence.

Jos

[UEZ]

I had a quick look to the abbreviations and found really nice features.

Now I've to remember all the abbreviations and use it when typing some code lines.

Very useful!

Br,
UEZ

[Valik]

This can be done via LUA by using OnUpdateUI(). It will require some proper testing to ensure it won't be constantly lexing the output shown in the Outputpane.
Just for having a play with this I started to add some Annotations logic in AutoIt3Wrapper, were I capture the au3check output.
I am not so sure this is really going to improve things but got some basics working.

Jos, right now I'm more interested in understanding why warnings are not showing up styled correctly. Errors work fine but not warnings. I don't know if it's a SciTE bug or if it doesn't like how Au3Check formats it's warnings. Sort that out and then I can think up something on how to get the inline errors to show up when desired.

[Jos]

Jos, right now I'm more interested in understanding why warnings are not showing up styled correctly. Errors work fine but not warnings. I don't know if it's a SciTE bug or if it doesn't like how Au3Check formats it's warnings. Sort that out and then I can think up something on how to get the inline errors to show up when desired.

Warnings are being shown with the same color as Errors for me.
Do you have an example where it doesn't work so I can check if it has something to do with the lexing?

[Melba23]

Jos,

I have just reinstalled v3.3.8.0 and SciTE4AutoIt3 (including the 3.02 beta) and I seem to have lost a lot of your "magic". Abbreviations no longer colour and can only be expanded by Ctrl-B and not SPACE; the colours no longer work in the lower pane:

ConsoleWrite('! = Bold Red' & @LF)
ConsoleWrite('> = Blue' & @LF)
ConsoleWrite('- = Orange' & @LF)
ConsoleWrite('+ = Green' & @LF)
ConsoleWrite('(5) : = Red (jump to line 5 when double-clicked)' & @LF)
ConsoleWrite('Start with String or Integer then ' & @TAB & '6' & ' = Pink (jump to line 6 when double-clicked)' & @LF)
ConsoleWrite('(' & @ScriptLineNumber & ') : = Red (jump to line ' & @ScriptLineNumber & ' when double-clicked)' & @CRLF)

The "jump to line" still works, but it is all mono-chrome.

What have I done - and how do I get it back!

M23

[Jos]

Here's what I came up with:

error.inline=1
style.error.1=fore:#FF0000,back:#FFFF00
style.error.2=fore:FFFFFF,back:#FF0000

However, there's a bug either with the error.inline feature or with Au3Check. It detects error messages just fine. It draws the line with a red background and white text. It does not detect warnings, though. It draws those in the style.error.0 style instead of style.error.1.

Note: To see this feature in action insert some errors into a script and then run Au3Check. After it is complete double-click on an error line in the output pane and you should see all the errors show up inline with the document as well.

Edit: Wow the feature needs work. My expected behavior is for the errors to show up after running Au3Check. I also expect re-running Au3Check to clear the errors. Doesn't happen. Instead it's possible to get stuck with an orphaned error in the document which won't go away even though the code has been fixed.

Look at this and this is indeed a nice option.
Need to check for a better way to clear the errors because clearing all bookmarks is not a real good option.

Jos

Edited by Jos, 24 January 2012 - 10:36 PM.

[Valik]

Warnings are being shown with the same color as Errors for me.
Do you have an example where it doesn't work so I can check if it has something to do with the lexing?

Actually it's probably using style.error.0 which is the default style. Make sure you set up style.error.0, style.error.1 and style.error.2 with unique colors so you can tell them apart. Then test with the following code which produces 1 warning and 2 errors:

If $var = "" Then ConsoleWrite("Error")

Error()

Right now all I'm seeing are lines styled with style.error.0. It seems to be ignoring style.error.1 and style.error.2 (I thought I had style.error.2 working a few days ago).

Edited by Valik, 24 January 2012 - 10:05 PM.
Fixed incorrect property name.

[Jos]

What have I done - and how do I get it back!

Sounds like you are still using the LITE version...
check your properties files if they are all still in order.

[guinness]

Jos, did you update SciTEGlobal.properties in the SciTE 3.02 folder too?

[Jos]

[/autoit]
Right now all I'm seeing are lines styled with style.error.0. It seems to be ignoring style.error.1 and style.error.2 (I thought I had style.error.2 working a few days ago).

Looks like we need to change the warning and error messages to lowercase to make it work.
Just update the outputpane messages to lowercase and double click them again... they change then to the correct color.

Did a quick update of the au3check and that looks better. uploaded a copy to the SciTE beta directory (not updated the version yet)
Need to check for a better way to clear the errors because clearing all bookmarks is not a real good option.

Edited by Jos, 24 January 2012 - 10:37 PM.

[Jos]

Jos, did you update SciTEGlobal.properties in the SciTE 3.02 folder too?

Guess this is rhetorical
Fixed that one as well.

Thanks

[guinness]

You're welcome.