Jos

Is this a fact or your guess as I don't see any proof during my quick scan of this thread, or did I miss that?

Sorry, hadn't seen this one as I was avoiding this topic after seeing only questions and no clear answers! Anyway, no idea what you are asking me, as I do not know what "doesn't work" means and am too lazy to start trying to sort out what it could mean! 😉

On Win11 Home Alt and the Space work fine for me with SciTE 32 v5.5.6.

Nice to see such a descriptive result. I am sure you will figure it out.

For starters: disable upx and try again as often the AV on your system will stop Programs that used upx.

Did you search & update? 😉

Guess you mean "SciTE Jump", which comes with the full SciTE4AutoIt3 installer? It is in the Tools dropdown when installed.

I was just trying to figure out what that extra info really contributes! 😉

... so there is an issue with that too?

I haven't read the whole thread as it isn't concrete enough for me and not looking for a puzzle at the moment. The title talks about a Save-lag so what is this snipped supposed to do?

Updated v25.205.1420.14 available in Beta.

So the change that is proposed is like this at line 2000 in Autoit3Wrapper v 25.205.1420.13 ?:                 ; SET DEFAULT TO WIN10 when not specified                 If $INP_Res_Compatibility = "" Then $INP_Res_Compatibility = "Win10"                 If $INP_Res_Compatibility <> "ignore" Then                     FileWriteLine($hTempFile2, '    <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">')                     FileWriteLine($hTempFile2, '        <application>')                     If StringInStr($INP_Res_Compatibility, "Win10") Then                         FileWriteLine($hTempFile2, '            <maxversiontested Id="10.0.18362.1"/>')                         FileWriteLine($hTempFile2, '            <!--The ID below indicates application support for Windows Vista -->')                         FileWriteLine($hTempFile2, '            <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>')                         FileWriteLine($hTempFile2, '            <!--The ID below indicates application support for Windows 7 -->')                         FileWriteLine($hTempFile2, '            <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>')                         FileWriteLine($hTempFile2, '            <!--The ID below indicates application support for Windows 8 -->')                         FileWriteLine($hTempFile2, '            <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>')                         FileWriteLine($hTempFile2, '            <!--The ID below indicates application support for Windows 8.1 -->')                         FileWriteLine($hTempFile2, '            <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>')                         FileWriteLine($hTempFile2, '            <!--The ID below indicates application support for Windows 10 -->')                         FileWriteLine($hTempFile2, '            <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>')                         _Write_RC_Console_Msg("Setting Program Compatibility Manifest information to Windows10", "", "...", 0)

I am fine with that too as long as it all makes sense and is useful for most.

When it is a generic change we should make and works for all win10 compiled scripts, then obviously the change can be made. Just give me the details of the change for the current Autoit3Wrapper.au3, and I will make those changes. 🙂 Cheers, Jos

I am sure he's happy after 5 years!!! 😉