Leaderboard

The starting point is that any UDF starting with 2 underscores is considered an internal UDF and will not be colored/recognised unless it exists in the same file. This means that the FAST search using the tables will work in wdcore.au3, but not in any other file, even when there is an include. Having said that, I agree it should then try to old "long route" which opens the current included files and check for the UDF, which indeed wasn't working correctly. That last part is fixed in the latest version included in the ZIP.

Standard SciTE functionality is that the files defined in au3.properties for the *.au3 extension are read: # List of all AutoComplete API files used api.$(au3)=$(SciteDefaultHome)\api\au3.api;$(SciteDefaultHome)\api\au3.autoit3wrapper.api;$(SciteUserHome)\au3.std.dynamic.calltips.api;$(SciteUserHome)\au3.file.dynamic.calltips.api;$(SciteUserHome)\au3.usr.dynamic.calltips.api;$(SciteUserHome)\au3.user.calltips.api # List of all AutoComplete API files used api.$(au3)= $(SciteDefaultHome)\api\au3.api; ### Is installed/updated by the AutoIt3 Installer with the standard UDF's, directives, functions $(SciteDefaultHome)\api\au3.autoit3wrapper.api; ### Is installed/updated by the SciTE4AutoIt3 Installer with the SciTE Directives $(SciteUserHome)\au3.std.dynamic.calltips.api; ### Dynamic process generated $(SciteUserHome)\au3.file.dynamic.calltips.api; ### Dynamic process generated $(SciteUserHome)\au3.usr.dynamic.calltips.api; ### Dynamic process generated $(SciteUserHome)\au3.user.calltips.api ### Hardcoded User Calltips as defined in the Helpfile, SciTEConfig addon. So the process would have to override this setting to point to another file which is created as previously defined, so SciTE will only look at that.

No worries, I appreciate the feedback from you all as that is part of the motivation to keep pushing this to a real production version one day! So thanks for the "harassing".

The standard supplied api files stay as they are, but are read at the start to determine the delta with everything found. All other found usfs are saved in different apu files dynamically by the lua code.

Correct... and just found the name in a PM with the question about the max length from him. .... so memory was correct, just to wrong name associated with it . 🤔wonder why that is... but the answer could be that you will have the re-write all API files and adapt the length of the text appearing on the second line. A process I believe could be to perform these steps : Read all current API files. Determine the correct max length for the text, insert the \n and write it to a new file. Update the settings to use only this one api file. Some of it is already there in the current dynamic stuff .... Jos

Guess it must have been that other "SciTE Beta Tester we have around here" that asked it.

I have the impression that the ctrl+z behavior is buildin as there is no check for that anywhere in the scripts. As to your second question: didn't you ask that before and also posted it on the official SciTE group?