BETA: SciTE v5x & lua Dynamic_include and "Smart" AutoComplete for Vars/UDFs/Abbrevs

[donnyh13]

Doing a quick test, it seems "\n" isn't interpreted when read from the api file.

[Jos]

Thought I tested that a while ago.... so sorry for the misguidance there. Will have a look when I have some time whether this is possible or not.

Edit: You have to set this property to allow escaped characters in the text:

calltip.au3.use.escapes=1

after which an \n does work.  

 

calltip.lexer.use.escapes calltip.*.use.escapes

When set to 1 the API file may contain C style backslash escapes which are listed in the command line arguments section. The * form is used if there is no lexer specific setting.

Edited January 9 by Jos

[mLipok]

btw.
how actually this following property

Quote

proper.case

works with dynamic LUA ?
 

Edited January 9 by mLipok

[Jos]

57 minutes ago, mLipok said:

how actually this following property

Not sure what the question is, but it should still work the way it has always worked:

• UDF's: It takes the proper case from au3.api for the standard UDF's / Macro's / Functions and of any extra UDF the Casing of the Func XYZ() line. 
• VAR's: It takes the first Global/Local/Dim definition it finds or else the first $VAR= line. 

[mLipok]

1 hour ago, Jos said:

UDF's: It takes the proper case from au3.api for the standard UDF's / Macro's / Functions and of any extra UDF the Casing of the Func XYZ() line. 

why not from:   .SciTE_Dynamic_fileUDFs.tbl
?

1 hour ago, Jos said:

VAR's: It takes the first Global/Local/Dim definition it finds or else the first $VAR= line. 

as I understand your answer from current au3 file ?

if I'm right
why not from:    .SciTE_Dynamic_fileVARs.tbl 
?

[Jos]

My previous post was about where the proper case info is coming from and your question feels like it is about how the update process works after a word is completed....2 different things!

Why these questions about a process without knowing the fundamentals of it ? Is something not working?  😉

Edited January 9 by Jos

[mLipok]

I'm just cleaning things up because as I noticed, I don't have PROPER CASE in the code everywhere.
That's why for now I'm just observing the program from this angle.

After testing, I see that when I type const name or function name it now works OK (accordingly to created dynamic file tables).
But you know, I've been using SciTE4Au3 + DYNAMIC LUA from the beginning... and since I still have so many incorrect ones (func/var names), therefore I just wonder why the old incorrect names (with incorrect sizes) still persist.

Going further, I checked how TIDY works.
And after checking, I wonder:

If Tidy.exe   could also use:  .SciTE_Dynamic_fileVARs.tbl and .SciTE_Dynamic_fileUDFs.tbl ?
btw. my Tidy.ini:
 

Quote

[ProgramSettings]
 * * *  Update Functions/Keywords/Macros/UDFs to Proper case
proper=1

 * * * Update Constants defined in the "constant Include files"
properconstants=1
 

 

Edited January 9 by mLipok

[mLipok]

I also notice one a slightly distracting inconvenience

When I try to jump to function:

_LOWriter_DocOpen

It opens proper file (LibreOfficeWriter_Doc.au3) but in tab I see little missliging name and path:


the above example screenshot shows that the path is written in lowercase, while correctly it should look like this:

What I mean is that it shows the file name as it was called and not as its actual name in the file system.

However,
I think this is an internal problem with SciTE by Neil Hodgson
 

Edited January 9 by mLipok

[mLipok]

40 minutes ago, Jos said:

My previous post was about where the proper case info is coming from and your question feels like it is about how the update process works after a word is completed....2 different things!

Normal thing, action and reaction.
Your comment triggered my "twisted" thought process

 

[Jos]

1 hour ago, mLipok said:

If Tidy.exe   could also use:  .SciTE_Dynamic_fileVARs.tbl and .SciTE_Dynamic_fileUDFs.tbl ?

Not going to happen as that is a total different/ separate process that does it's own thing and I honestly do not see why & How that would ever work properly.

Things should work already correctly with Tidy...no?

[Jos]

1 hour ago, mLipok said:

What I mean is that it shows the file name as it was called and not as its actual name in the file system.

However,
I think this is an internal problem with SciTE by Neil Hodgson

Not sure about that as in lua things are matched case sensitive so it could very well be the code makes all lower case before matching. Not so much worries about File/Path casing in this process.  

[donnyh13]

8 hours ago, Jos said:

after which an \n does work

Ah, thanks. I went through all the hits for call tip in the help file and thought I had found a setting like that, but after my research I couldn't find it again for the life of me! Sorry about the false report. Thanks for the guidance.

 

Edited January 9 by donnyh13

[Jos]

2 hours ago, donnyh13 said:

Sorry about the false report. Thanks for the guidance.

No worries, and the thing to remember is that the LUA scripts currently generate a text that contains the full include path meaning it contains a single backslash, which will result in a "wrong" text in case you enable this. 

[Jos]

I've just uploaded a update of SciTE_changes_Dynamic_Includes_LUA.zip:

• updated the goto UDF process a bit with hopefully a cleaner result.
• Updated the Switch tabs logic so the FileUDFs are properly loaded one time and cached. Cache is updated on Save.
  The previous process was such that syntax highlighting wouldn't work anymore after saving another au3 file and then swapping to another AU# file tab.
  This was bugging me for a while now so hopefully dealt with that bug now. 

Jos

[Jos]

19 hours ago, donnyh13 said:

Ah, thanks. I went through all the hits for call tip in the help file and thought I had found a setting like that, but after my research I couldn't find it again for the life of me! Sorry about the false report. Thanks for the guidance.

Just for fun had a look at this and have the basics working to set a max length (in this case to 100:

This Max length is applied to both the parameters and the text in case they are longer than the defined length with:

# Max line length of Params and Description - default no max
AutoComplete_Calltip_MaxLineLen=100

I am still testing, but will include it soon in the zip file. 

 

edit: example of current default behavior which doesn't show everything in the available displayed part:

and when I set AutoComplete_Calltip_MaxLineLen=150:

Edited January 10 by Jos

[mLipok]

Awesome.
This should fix one of my issue reported quite a long time ago.
When I use 2 monitors the calltip goes beyond the scope of one monitor and appears on the other.

Edited January 10 by mLipok

[donnyh13]

59 minutes ago, Jos said:

basics working to set a max length

That's amazing! Thanks so much Jos! That's been an annoyance for me for a while.

Edited January 10 by donnyh13

[Jos]

Just uploaded some updated LUA scripts in the ZIP file with these changes:

• Fix reloading the API info for the current file when switching between open scripts in SciTE
• Added option to set the max line length of the Calltip paramaters and Description lines, to make them wordwrap & indent when longer.
  Set this parameter in you SciTEUser.properties to the max length you prefer (default is no wordwrap):

  # Max line length of Params and Description - default no max
  autocomplete_calltip_maxlinelen=150
  # following is overridden by the scripts when MaxLineLen is set and set to 1
  # calltip.au3.use.escapes=1

   

[donnyh13]

Works great Jos! Thank you again. 👍

[mLipok]

@Jos it works very good.

Please consider making the first line adjust accordingly to the width of the rest.

EDIT: I mean that the name of the function affects the width of the displayed text in the first line.

Edited January 10 by mLipok