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

[argumentum]

12 minutes ago, Jos said:

Should be fixed in the current zips available.

Tested both x86 and x64. All good. (24H2 26100.1000)

[argumentum]

..OCD. Just saw this video and decided to give it a try, just in case the latest and the greatest, ..is not so great. But again, all good.
Running it,  by copy and paste the AutoIt3 folder, from the other older 24H2 to this fresh install. Nice.

[Jos]

@water @mLipok  did one of you had a chance to check things or gotten it working in x86?

[water]

Hi Jos,

Did the following steps to test the x86 version:

• Backup of the current SciTE directory
• Deleted all files in the current SciTE directory
• Deactivated the Microsoft Defender SmartScreen
• Installed the latest SciTE 5.4.0 as described in your first post
• Executed SciTE.exe ==> works fine
• Unzipped your latest 86x ZIP and copied the 3 files (5.5.3.0) to the SciTE directory (overwriting the 5.4.0 files)
• Windows security tells me that the App I try to INSTALL has not been downloaded from the MS App Store and is not verified. Even when I ignore the message and select "INSTALL anyway" SciTE pops up for half a second and then closes again.

As I'm rather new to Windows 11 this problem might be caused by me

Edited November 6 by water

[water]

I had a look at the EventViewer and found the following entry. Seems to be a problem with the MSVCP140.dll.

 

On 8/22/2024 at 6:23 PM, argumentum said:

... if the user forgets to unblock the files downloaded containing executable flies,

I unblocked the Scintilla.dll and lexilla.dll but got the same error.

 

Edited November 6 by water

[Jos]

We've seen that c5 memory corruption error before in this thread, which pointed to some "wrong" version of  the MSVCP140.DLL.

 

Thanks for you help trying to find the issue. 😀

Edited November 6 by Jos

[donnyh13]

Hi Jos,
I was able to reproduce both errors again, sort of, the one didn’t end with the same message, but I was able to cause the error with logging. I still cannot reproduce it reliably though.
     Not sure if this will help any? The first error, where the script just ends as if it hit the end normally, has this in Scite output with debugging:

>AutoIt3Wrapper_Watcher1396-->AutoIt3Wrapper_RunUserScript1744: rc:17833895689 er:0 Text:#$#Ping:WATCHER#$#
+AutoIt3Wrapper_Watcher1396-->AutoIt3Wrapper_RunUserScript1744 Text:#$#Ping:WATCHER#$#
->>>>>> AutoIt3Wrapper_RunUserScript1744 (m) received data: #$#Ping:WATCHER#$#|Ping|WATCHER
>AutoIt3Wrapper_Watcher1396-->AutoIt3Wrapper_RunUserScript1744: rc:0 er:3 Text:#$#Ping:WATCHER#$#
!AutoIt3Wrapper_Watcher1396-->AutoIt3Wrapper_RunUserScript1744: Error=3 Text:#$#Ping:WATCHER#$#
->>>>>>> AutoIt3Wrapper_Watcher1396 (w) No Ping response from : AutoIt3Wrapper_RunUserScript1744
>AutoIt3Wrapper_Watcher1396-->0: rc:0 er:1 Text:#$#Stop:WATCHER#$#
!AutoIt3Wrapper_Watcher1396-->0: Error=1 Text:#$#Stop:WATCHER#$#
->>>>>>> No responce from MasterScript.
-> Watcher: Stop: Sending WinClose to your script with Pid 2432
->>>>>> Script must have ended as STDOUT & STDERR are closed
>
+>13:16:22 AutoIt3 ended. rc:0
---< Master _OnAutoItExit() 1744"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.au3" /run /prod /ErrorStdOut /in "C:\Users\Owner\Desktop\Libre Office Scripts\Script - Copy.au3" /UserParams    
>AutoIt3Wrapper_Watcher1396-->AutoIt3Wrapper_RunUserScript1744: rc:0 er:1 Text:#$#ScriptEnded#$#
!AutoIt3Wrapper_Watcher1396-->AutoIt3Wrapper_RunUserScript1744: Error=1 Text:#$#ScriptEnded#$#
-##> Close |AutoIt3Wrapper_Watcher1396| (w) (IPC @error=0)
---< Watcher _OnAutoItExit() 1396"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.au3" /Watcher 1744 2432
+>13:16:23 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 1380.9707

And the second error when it closes while a blocker is open, in this case it is a LibreOffice Macro dialog, though I’ve had it happen with a MsgBox before. In this case my script had some AU3 warnings, I left them in case they helped reproduce the error, but so far it doesn’t make it any more reliable. Scite had an output like this:

>"C:\Program Files (x86)\AutoIt3\SciTE\..\AutoIt3.exe" "C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.au3" /run /prod /ErrorStdOut /in "C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3" /UserParams    
+>10:17:50 Starting AutoIt3Wrapper (pid=1360) 23.402.1150.10 from:SciTE.exe (0.0.0.0)  Keyboard:00000409  OS:WIN_7/Service Pack 1  CPU:X64 OS:X64  Environment(Language:0409)  CodePage:0  utf8.auto.check:4
+>         SciTEDir => C:\Program Files (x86)\AutoIt3\SciTE   UserDir => C:\Users\Owner\AppData\Local\AutoIt v3\SciTE\AutoIt3Wrapper   SCITE_USERHOME => C:\Users\Owner\AppData\Local\AutoIt v3\SciTE
>Running AU3Check (3.3.16.1)  params:-d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7  from:C:\Program Files (x86)\AutoIt3  input:C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3
"C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3"(309,43) : warning: $sName: declared, but not used in func.
Func _LOWriter_FormAdd(ByRef $oObj, $sName)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
"C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3"(314,35) : warning: $sTempName: declared, but not used in func.
    Local $sTempName = "AutoIt_FORM_"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
"C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3"(315,19) : warning: $iCount: declared, but not used in func.
    Local $iCount = 1
    ~~~~~~~~~~~~~~~~~^
C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3 - 0 error(s), 3 warning(s)
->10:17:52 AU3Check ended. Press F4 to jump to next error. rc:1
>Running:(3.3.16.1):C:\Program Files (x86)\AutoIt3\autoit3.exe "C:\Autoit Scripts\Autoit\AutoIt stuff Jan 2022\LibreOffice Writer Test Scripts\Writer Testing.au3"    
+>Setting Hotkeys...--> Press Ctrl+Alt+Break to Restart. --> Press Ctrl+BREAK to Stop.
>
+>10:18:22 AutoIt3 ended. rc:0
+>10:18:22 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 32.5800

And an error log with this:

2024-11-17 10:18:19 : >AutoIt3Wrapper_Watcher3748-->AutoIt3Wrapper_RunUserScript1360: rc:50469277137 er:0 Text:#$#Ping:WATCHER#$#
2024-11-17 10:18:19 : +AutoIt3Wrapper_Watcher3748-->AutoIt3Wrapper_RunUserScript1360 Text:#$#Ping:WATCHER#$#
2024-11-17 10:18:19 : ->>>>>> AutoIt3Wrapper_RunUserScript1360 (m) received data: #$#Ping:WATCHER#$#|Ping|WATCHER
2024-11-17 10:18:20 : >AutoIt3Wrapper_Watcher3748-->AutoIt3Wrapper_RunUserScript1360: rc:0 er:3 Text:#$#Ping:WATCHER#$#
2024-11-17 10:18:20 : !AutoIt3Wrapper_Watcher3748-->AutoIt3Wrapper_RunUserScript1360: Error=3 Text:#$#Ping:WATCHER#$#
2024-11-17 10:18:20 : ->>>>>>> AutoIt3Wrapper_Watcher3748 (w) No Ping response from : AutoIt3Wrapper_RunUserScript1360
2024-11-17 10:18:20 : >AutoIt3Wrapper_Watcher3748-->0: rc:0 er:1 Text:#$#Stop:WATCHER#$#
2024-11-17 10:18:20 : !AutoIt3Wrapper_Watcher3748-->0: Error=1 Text:#$#Stop:WATCHER#$#
2024-11-17 10:18:20 : ->>>>>>> No responce from MasterScript.
2024-11-17 10:18:20 : -> Watcher: Stop: Sending WinClose to your script with Pid 4420
2024-11-17 10:18:21 : > Detected your script is still running but AutoIt3Wrapper was closed.
2024-11-17 10:18:22 : - Script still running, so now Killing running script Pid 4420
2024-11-17 10:18:22 : ->>>>>> Script must have ended as STDOUT & STDERR are closed
2024-11-17 10:18:22 : ---< Master _OnAutoItExit() 1360"C:\\\\Program Files (x86)\\\\AutoIt3\\\\SciTE\\\\AutoIt3Wrapper\\\\AutoIt3Wrapper.au3" /run /prod /ErrorStdOut /in "C:\\\\Autoit Scripts\\\\Autoit\\\\AutoIt stuff Jan 2022\\\\LibreOffice Writer Test Scripts\\\\Writer Testing.au3" /UserParams    
2024-11-17 10:18:23 : ---< Watcher _OnAutoItExit() 3560"C:\\\\Program Files (x86)\\\\AutoIt3\\\\SciTE\\\\AutoIt3Wrapper\\\\AutoIt3Wrapper.au3" /Jump2FirstError 1360
2024-11-17 10:18:23 : > Done with cleanup.
2024-11-17 10:18:23 : >AutoIt3Wrapper_Watcher3748-->AutoIt3Wrapper_RunUserScript1360: rc:0 er:1 Text:#$#ScriptEnded#$#
2024-11-17 10:18:23 : !AutoIt3Wrapper_Watcher3748-->AutoIt3Wrapper_RunUserScript1360: Error=1 Text:#$#ScriptEnded#$#
2024-11-17 10:18:23 : -##> Close |AutoIt3Wrapper_Watcher3748| (w) (IPC @error=0)
2024-11-17 10:18:23 : ---< Watcher _OnAutoItExit() 3748"C:\\\\Program Files (x86)\\\\AutoIt3\\\\SciTE\\\\AutoIt3Wrapper\\\\AutoIt3Wrapper.au3" /Watcher 1360 4420

 

[Jos]

@donnyh13,

Still feels like some race condition, so I have added some logic that the "IPC ping" needs to fail 3 times now before it is assumed that the other process must have ended.
So the watcher task gives the other process(es) running the userscript a bit more time to handle the userscript ending. (I hope)

Could you please test with this version of AutoIt3Wrapper.au3 to check if you still can make things fail?

Thanks

Edited November 18 by Jos

[donnyh13]

Sure Jos, Thanks for the modifications.

Sorry for the delay, I just got a chance to check back here. I will begin testing, and report back.

[donnyh13]

I can't say it's fixed for sure, but I haven't hit the problem yet anyway!

Thanks Jos!

[maniootek]

I've recently installed the SciTE4AutoIt3 Beta v5.4.0 from this post.

However, I’ve encountered an issue while coding: whenever I press the Enter key, the line I’m currently typing on jumps to the very top of the editor. This behavior is quite disruptive, and I’d like to disable this feature.

I’ve checked the settings and documentation but haven’t found a solution yet. Could someone guide me on how to turn off this behavior? Is there a specific configuration or setting I need to adjust?

[Jos]

Try disabling the indentation fix routines by modifying SciTEStartup.lua:

-- Load all the Lua files.
LoadLuaFile("Class.lua")    -- Always load first.
LoadLuaFile("Common.lua")   -- Always load second.
LoadLuaFile("AutoItPixmap.lua")
LoadLuaFile("AutoHScroll.lua")
LoadLuaFile("AutoItAutoComplete.lua")
--LoadLuaFile("AutoItIndentFix.lua")
LoadLuaFile("EdgeMode.lua")
LoadLuaFile("Tools.lua")
LoadLuaFile("AutoItTools.lua")
LoadLuaFile("AutoItDynamicIncludes.lua")
LoadLuaFile("AutoItGotoDefinition.lua")
LoadLuaFile("SciTE_extras.lua")

In case you want to contribute, you could activate the lua file and enable the debugging by adding this line to SciTEUser.properties:

debug.autoitindentfix=y

.. then edit the file in a way this issue occurs and  supply me with a zipped up copy of the failing file and debug log: %localappdata%\AutoIt v3\SciTE\SciTE_LUA_Scripts_Debug.err
so I can do some debugging.

Thanks,
Jos

[donnyh13]

Hi Jos,

I noticed that there is a potential bug(?) with the Auto-Complete functionality, though not particularly detrimental. Particularly when auto-completing variables that replace other variables that are using dot access (such as with Objects). Normally if the variable has the same ending, the whole variable will be replaced when auto-completing, but with variables using dot notation, the dot notation is included in the check if the variable ends the same, and consequently the check returns false, when it should be true.

An example script:

Local $oTest11Obj, $oTest12Obj


$oTest12Obj.Testing()

When attempting to auto-complete while changing the variable $oTest12Obj to $oTest11Obj the following is reported:

Quote

--> 901 $otest11obj Obj.Testing false

And the following auto-complete results:

$oTest11ObjObj.Testing()

I would guess that temporarily removing the period from word characters would fix that? But I’m not sure if that would be detrimental or not in other instances.

Thanks,

Donny

[Jos]

Could you test this piece of code in your setup?
Open file AutoItAutoComplete.lua andchange this part on line 661:

-- print("-->",endPos, str:sub(-1 * reststring:len()):lower(), reststring, (str:sub(-1 * reststring:len()):lower() == reststring:lower()) )
                -- move the cursor to the end when equal

to: 

-- print("-->",endPos, str:sub(-1 * reststring:len()):lower(), reststring, (str:sub(-1 * reststring:len()):lower() == reststring:lower()) )
                self:DebugPrint("OnUserListSelection>",endPos, str:sub(-1 * reststring:len()):lower(), reststring, (str:sub(-1 * reststring:len()):lower() == reststring:lower()) )
                -- fix DOT in reststring word
                if reststring:find('%.') then
                    editor:SetTargetRange(endPos, editor:WordEndPosition(endPos, true)-reststring:len()+reststring:find('%.')-1)
                    reststring = reststring:sub(1,reststring:find('%.')-1)
                    self:DebugPrint("Fixed DOT in variable >",endPos, str:sub(-1 * reststring:len()):lower(), reststring, (str:sub(-1 * reststring:len()):lower() == reststring:lower()) )
                end
                -- move the cursor to the end when equal

 
Let me know if that fixes it for you so I can update the source.
Cheers,
Jos

[donnyh13]

That fixed it so far. I'll keep testing to see if there are any anomalies otherwise. Thanks Jos.

[maniootek]

On 12/9/2024 at 3:22 PM, Jos said:

Try disabling the indentation fix routines by modifying SciTEStartup.lua:

-- Load all the Lua files.
LoadLuaFile("Class.lua")    -- Always load first.
LoadLuaFile("Common.lua")   -- Always load second.
LoadLuaFile("AutoItPixmap.lua")
LoadLuaFile("AutoHScroll.lua")
LoadLuaFile("AutoItAutoComplete.lua")
--LoadLuaFile("AutoItIndentFix.lua")
LoadLuaFile("EdgeMode.lua")
LoadLuaFile("Tools.lua")
LoadLuaFile("AutoItTools.lua")
LoadLuaFile("AutoItDynamicIncludes.lua")
LoadLuaFile("AutoItGotoDefinition.lua")
LoadLuaFile("SciTE_extras.lua")

In case you want to contribute, you could activate the lua file and enable the debugging by adding this line to SciTEUser.properties:

debug.autoitindentfix=y

.. then edit the file in a way this issue occurs and  supply me with a zipped up copy of the failing file and debug log: %localappdata%\AutoIt v3\SciTE\SciTE_LUA_Scripts_Debug.err
so I can do some debugging.

Thanks,
Jos

Before I disabled the option you mentioned I noticed this message in my console:

Quote

... Files (x86)\AutoIt3\SciTE\Lua\AutoItDynamicIncludes.lua:682: attempt to concatenate a nil value (field 'MaxIncludes2Read')
... Files (x86)\AutoIt3\SciTE\Lua\AutoItDynamicIncludes.lua:2105: attempt to compare nil with number

Now after I commented line

Quote

LoadLuaFile("AutoItIndentFix.lua")

my console show only

Quote

... Files (x86)\AutoIt3\SciTE\Lua\AutoItDynamicIncludes.lua:682: attempt to concatenate a nil value (field 'MaxIncludes2Read')

so there is no more warning like this:

Quote

... Files (x86)\AutoIt3\SciTE\Lua\AutoItDynamicIncludes.lua:2105: attempt to compare nil with number

also there is no scroll issue when I hit Enter key

Unfortunatelly, after enabling logging, there is no such a file

On 12/9/2024 at 3:22 PM, Jos said:

%localappdata%\AutoIt v3\SciTE\SciTE_LUA_Scripts_Debug.err

[Jos]

2 hours ago, maniootek said:

Before I disabled the option you mentioned I noticed this message in my console:

Quote

... Files (x86)\AutoIt3\SciTE\Lua\AutoItDynamicIncludes.lua:682: attempt to concatenate a nil value (field 'MaxIncludes2Read')
... Files (x86)\AutoIt3\SciTE\Lua\AutoItDynamicIncludes.lua:2105: attempt to compare nil with number

 

Think this was fixed in the updated lua files in this linked zip file. I haven't updated the Installer and portable zip files yet. 
This issue has to do with the fact you haven't copied all possible SciTEUser.properties options as defined in the first post. (which it should be able to handle)

 

[maniootek]

2 hours ago, Jos said:

Think this was fixed in the updated lua files in this linked zip file. I haven't updated the Installer and portable zip files yet. 
This issue has to do with the fact you haven't copied all possible SciTEUser.properties options as defined in the first post. (which it should be able to handle)

 

I copied properties options from first post to my SciTEUser.properties and now problem is fixed. No warnings in the console and no problem with page scrolled when I hit Enter key. Thank you

[maniootek]

... but I have another problem which is CTRL + Z (undo) does not undo last operation but many last operations

[Jos]

4 hours ago, maniootek said:

... but I have another problem which is CTRL + Z (undo) does not undo last operation but many last operations

Works fine for me, but I guess you need to provide context when reporting an issue, not just a simple statement like this.