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

[mLipok]

I have such problem:

Quote

+>21:32:47 Script started, waiting for output. (pid=30052) 6
->>>>>> Admin not responding so close master pid:30052 err:4
+>21:32:49 AutoIt3Wrapper Finished.

I see the request to accept UAC . I accept them.
Very often but not always I get "Admin not responding so close master".

Any idea why this happens ?

Edited April 7 by mLipok

[Jos]

54 minutes ago, mLipok said:

Any idea why this happens ?

I need to take a closer look at that and let you know when I had a free moment to check, as that messages seems to be obsolete and should be debug only.

The process is working fine, and it is just this message that appears now and then when ending the Master Script? 

Edited April 7 by Jos

[Jos]

On 4/7/2024 at 10:31 PM, Jos said:

The process is working fine, and it is just this message that appears now and then when ending the Master Script? 

So, is it working fine and just displaying this message sometimes? Please confirm.   
Thanks  

[mLipok]

I found issue with calltips.

 

Please try this snippet:

_ArrayDisplay($aTest, "TITLE")
_ArrayDisplay($aTest, "TITLE (v2)")

place the cursor on v2 inside this bracket, try to bring caltips with CTRL+SHIFT+SPACE

 

[Jos]

On 4/11/2024 at 10:00 AM, mLipok said:

I found issue with calltips.

Please try this snippet:

This is a core SciTE issue, so not much I am going to do something about, but is there any reason you don't answer the previous question before dumping the next one? 🙂   

Edited April 13 by Jos

[mLipok]

2 hours ago, Jos said:

is there any reason you don't answer the previous question before dumping the next one? 🙂   

Getting old , and overworked 🥺.

Will answer ASAP , when back from weekend vacation.

Edited April 13 by mLipok

[mLipok]

On 4/9/2024 at 10:25 AM, Jos said:

So, is it working fine and just displaying this message sometimes? Please confirm.   

I noticed this problem on two computers.
I have poor access to one of them, and on this one it always happens.

The thing is that it's a really old computer (it's probably a dozen or so years old).

[Jos]

The question is really whether the "problem" is that the message is displayed or also something else?

In other words: is everything working correctly?

[mLipok]

referring to my post:

Quote

+>21:32:47 Script started, waiting for output. (pid=30052) 6
->>>>>> Admin not responding so close master pid:30052 err:4
+>21:32:49 AutoIt3Wrapper Finished.

So I can't run the script, and this is a problem.

I had to use SHIFT+F5 instead F5, in order  to omnit AutoItWrapper.

Edited April 28 by mLipok

[Jos]

Ok, so it is really failing. Please share the total debug log with me so I can check what is happening. ... tnx  

(or if you know a way for me to replicate it would even be better!) 

Edited April 28 by Jos

[paw]

While 1
    ConsoleWrite("crashes after a while" & @CRLF)
WEnd

After having weird unexplainable crashes when running from SciTE, I tracked it down to the console, not sure why it crashes.

Using latest beta.

Spoiler

32-bit

Version 5.4.0   Scintilla:5.4.0   Lexilla:5.2.9

    Dec  3 2023 11:54:09

by Neil Hodgson.

 Updated by Jos

[Jos]

That doesn't surprise me that we will hit some sort of limit when you fire that many ConsoleWrite to the stdout.  AutoIt3Wrapper is an AutoIt3 script too and will require some processing time and isn't build for Mass STDOUT data. When I add a Sleep(10) in that loop, things work fine, so I am on the fence whether we simply need to live with this limitation or spent time in trying to debug whether it can be resolved at all.  

[paw]

Adding a sleep will just delay the crash, I originally ran it with Sleep(40) but removed it for faster reproducability and it still crashed after about 140 seconds which is barely 3500 lines, kind of making console debugging a game of chance.

I tried AutoIt3Wrapper (23.402.1150.0) and it hard crashed AutoIt with Error allocating memory after taking about 2 GB instead of silently failing. Also lasted much longer ~5 minutes instead of 34 seconds.

It was kind of ironic; by trying to find my bug, I made it worse by producing more console output 🥲

[Jos]

1 hour ago, paw said:

kind of making console debugging a game of chance.

Yeap... but guess you are on your own for that.  
Compile as Console and run the script from CMD prompt.

[donnyh13]

Hi Jos,

I may have found a minor bug for Autocomplete, or at least the part that collects the list of all Variable names.

Local $oTest1, $oText2

$oTest1

If you enter a period after $oTest1 (below the declaration), the autocomplete will come up with an option of "$oTest1," (including a comma). Otherwise the autocomplete doesn't show the one ending with a comma. Not sure if the variable including a comma at the end of it is intended or not?

 

Edit:

Also meant to say that my indenting changes are handy at times and a pain at other times. Especially after a continuation line, then it gets the indent level wrong. Also after commented lines using number pad comment.

Edited June 13 by donnyh13

[mLipok]

Stabilization ?
No more issues ?

 

Edited July 24 by mLipok

[Jos]

Honestly: I am not so sure if I really should continue the development of the Full SciTE version with all its pretty complex LUA script to support AutoIt3.
Maybe we should bundle the knowledge and build out the one of the current extension versions available for VSCode as VSCode is a real nice Editor?
 

Edited July 29 by Jos

[argumentum]

The idea is not bad. Is like delegating the editor maintenance to the VSCode crew. As long as we have the goodies that come with our version of SciTE, it should be just fine I guess.
There is a portable VSCode. I'll try it out.

[argumentum]

5 hours ago, Jos said:

Maybe we should bundle the knowledge and build out the one of the current extension versions available for VSCode

With a total of 30 min. of experience with VSCode... I feel like running back to SciTE

Not sure how "prime time" are those extensions. Again, 30 min. of experience.

[donnyh13]

On 7/29/2024 at 6:24 AM, Jos said:

Honestly: I am not so sure if I really should

I can hear you Jos, the Scripts you are having to maintain are very complex for sure to keep running correctly.

I'm not sure if you're asking everyone, or mainly Michal, if the latter, then sorry for the below 2 cents.

I can't speak from too much experience with both, but for what it's worth.... I have, of course used Scite for all of my AutoIt coding, and have grown fond and used to it, even having a few custom lua scripts to help make life easier. I have also used VSCode, for other projects and like many of its features. There are definitely pro's and Con's to both. I do like Scite for its simple layout, and plain display, just the necessities, and better performance (for me, anyway). Plus smaller download size. VSCode is handy for its many available plugins, and customization, but bigger install file size. Plus, a con for me, though not an impossibility, is Windows 7 isn't supported any more, so no more updates, but the rest still works fine, until they decide to cut something off.

How many features do you think would be lost if the switch was done? i.e. Keywords,(Emmet, I see), Header creator, tidy, "Smart" AutoComplete and call tips, etc., would they still be able to be integrated/re-created to work? I can see some would be as there are already a few people who have done VSCode plugins, Logan and Genius257, probably a few others, but just curious the extent. I haven't explored those plugins much. What about custom LUA scripts? That would be made more complex, I suppose, and be another language? ConsoleWrite etc., usage for debugging would probably change too?

Overall I would miss Scite. But if the features, or at least the main features could be added to VSCode too, I think the switch could be tolerable, if it makes it easier on you and the other devs to maintain.

Sorry, not much input. Maybe others will have more insightful comments.

Edited July 31 by donnyh13