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

[donnyh13]

Glad you solved the frustrating problem @mLipok. And also sorry to hear about the stresses and discouragements you have had to face in recent times. I am also glad to hear things are looking up for you.

I would also like to echo your sentiment, and thank Jos for his hard work on this (frequently) thankless task. I feel it has turned out great. A time or two I have reverted to Scite v4, and find I very quickly miss the new features of v5. Sorry for the discouragements Jos, and lack of testing/assistance at times. Wishing you the best in your future projects.

Best regards,

Donny

[donnyh13]

HI Jos,

I hit a minor bug (?) with AutoComplete, which I think you fixed once before, but can't find it in this thread.

If I begin with:

#include <MsgBoxConstants.au3>

And then Erase the "MsgBoxConstants" part to change the include to something else,

#include <.au3>

e.g. "FileConstants", if I select "FileConstants" in AutoComplete, AutoComplete leaves a ".au3>" at the end.

#include <FileConstants.au3>.au3>

 

[Jos]

I remember looking at this and there is a comment about it, but your scenario is still going wrong. try current beta lua script. 🙂  

[donnyh13]

33 minutes ago, Jos said:

try current beta lua script

That fixed it. Thanks Jos.

[IronFine]

Is it possible to disable the automatic adding of "(" after function autocomplete?

[Jos]

If/When you do not like the autocomplete functionaliteit for whatever reason you simply disable it.

[IronFine]

I do love the autocomplete, but every other IDE I am using (be it Visual Studio Code, Visual Studi, etc.) does not add the "(" after pressing TAB for autocompletion. If there is not option to disable the "(" I will just learn to re-train my muscle memory for SciTe

[Jos]

Not sure I understand the issue of inserting the ( after confirming the Autocompletion of a Function? That is the next required Character, isn't it?

On top of that, the auto insert of the "(" is also to allow the trigger for the popup of the parameters tooltip.

Edited July 3 by Jos

[IronFine]

Yes, you are absolutley right. It is gonna be the next character. And it is more about me being used to the ( not being automatically added in all the other IDE I am working with.

[WildByDesign]

I have been using v5 beta for many months now and have had zero issues on my machine. Thank you for everything, by the way.

So I decided to update my GitHub Actions workflow from the old SciTE4AutoIt3 to the latest SciTE4AutoIt3_vsc build that I use on my machine.

The workflow uses the /S silent switch to install it.

The problem is with the following:

- ### C:\Program Files (x86)\AutoIt3\SciTE\Au3Stripper\Au3Stripper.dat missing... Please get it from the website to make sure the Au3Stripper will work correctly.

I don't understand why Au3Stripper would specifically be looking for the Au3Stripper.dat file within C:\Program Files (x86)\ when it really should be looking in LocalAppData.

But I also don't understand why the old SciTE4AutoIt3 did not have this issue. Is there anywhere that I can tell Au3Stripper where to look for this file?

If it's available to download somewhere as a standalone file, I could download/copy the file to wherever it is looking for it.

[Jos]

2 hours ago, WildByDesign said:

I don't understand why Au3Stripper would specifically be looking for the Au3Stripper.dat file within C:\Program Files (x86)\ when it really should be looking in LocalAppData.

It checks for the environment variables "SCITE_USERHOME" and then "SCITE_HOME" and when they are not defined assumes a portable version is used so will default to the directory the AU3STRIPPER program is located in. 

[WildByDesign]

15 minutes ago, Jos said:

It checks for the environment variables "SCITE_USERHOME" and then "SCITE_HOME" and when they are not defined assumes a portable version is used so will default to the directory the AU3STRIPPER program is located in. 

Thank you, sir. Thanks to your response I was able to fix the workflow build for v5 beta.

[argumentum]

...so, what's in Au3Stripper.dat you asked @WildByDesign, ok,  

Functionname,Parameter to check,0=check for function/1=check for Variable
adlibenable,1,0
adlibregister,1,0
adlibunregister,1,0
call,1,0
dllcallbackregister,1,0
eval,1,1
guictrlregisterlistviewsort,2,0
guictrlsetonevent,2,0
guiregistermsg,2,0
guisetonevent,2,0
hotkeyset,2,0
isdeclared,1,1
objevent,2,0
onautoitexitregister,1,0
onautoitexitunregister,1,0
opt,2,0
traysetonevent,2,0
trayitemsetonevent,2,0

@Jos, that file, as far as I remember, is never touched/edited by users. Therefore it always uses the default values. Would it be a good idea to ignore it's absence if not found given that anyways a user has no idea of the benefit of changing it ( if there is any ) ?
We only use it for AutoIt. ( tho for what I see, it could be use for other coding languages too, hence the file to get the values from )

[argumentum]

6 minutes ago, argumentum said:

Would it be a good idea to...

..no, it wouldn't. I see why.
Then maybe add it to the beta folder for download ?

[WildByDesign]

For what it’s worth, I just ended up getting the workflow file to download https://www.autoitscript.com/autoit3/scite/download/Au3Stripper.zip

And from there, extract it to where Au3Stripper was looking for it, in this case Program Files (x86).

However if I did that step last, I would end up with outdated Au3Stripper. So I had to ensure that workflow extracted that first, then installs Scite4autoit3 beta after which gives me newer Au3Stripper and keeps the required DAT file there.

[Jos]

4 hours ago, argumentum said:

..no, it wouldn't. I see why.
Then maybe add it to the beta folder for download ?

Shouldn't be asking what the file really is used for and how it is maintained before making all these assumptions and suggestions? 😉

[argumentum]

..maybe. Is unlikely that anything will be added. Unless it's used for another coding language. I'd say that the last update was when AdlibRegister() got added/changed.
Then again only the .dat file needed update. But the .exe got updated much later again too. So for AutoIt, in my view that file is not a must. But I understand the the .dat file is better from a flexibility point of view, but could be disregarded when absent if the default values were in the .exe when used for AutoIt only.

Therefore knowing how to maintain it ... that is something that you'd do if needed ( there is no info in the help file for it ), and the need is unlikely to occur.
To me the current default setting could be in the .exe, but looking at it from what I believe is your point of view, made me say "..no, it wouldn't. I see why."

In any case, adding the .dat file to the beta folder is a not a bad idea.
  

[Jos]

Ok,  this is what it is:
au3stripper.exe requires the au3stripper.dat as that contains required input for it and these aren't in the program as a design choice at the time.
It comes with the installer or is part of the standard dowloadlink zipfile for au3stripper.
The Beta directory contains updated files to the standard installer, and this file isn't updated.

General advice: Don't cherry-pick anything from there when you aren't sure what the consequences are.