Jos

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!!! 😉

Isn't that the exact same question as previously? So NO it should not matter and if it does i like to understand the steps to reproduce the issue.

It will-should always have the latest AutoIt3 definitions when you install the separate SciTE4AutoIt3 version.

The lite version is simply just the SciTE editor that can do basic things and comes with the AutoIt3 installer. The Full version comes with many extras and is a separate installer. The latest version of the SciTE source is now part of the AutoIt installer, since that was recently updated, The latest full version is available in the Beta directory of SciTE4AutoIt3. I can't put things in production at the moment as I lack Edit access to the webpages after the last forum updates and are waiting for Jon to return from hibernation.

Not sure i understand what i am looking at. In general are the scite4autoit3 version standalone and compatible with the different version of autoit3 as the autoit3 configuration for scite is delivered withe the autoit3 installer.

There is no Tidy v3.3.18.0. Please provide the version of Tidy when reporting Tidy issue, but my wild guess would be you have a pretty old version that will generate a new table one time and that old version had an issue showing a log message in the console for each found func/macro etc Just let it run and finish, and it should not happen again, or even better use the current Beta version.

Just PM me or attach the updated LUA file when you have fixes, and I will merge them into my local version for the next upload. 🙂

I've tried to simply follow the rules that Tidy uses when it comes to indentation. In that case neither is perfect as this is the result with my tidy settings: Func _Test1() ;~ Local $123 ;# ;# ; A Comment ;# ;# EndFunc ;==>_Test1 Func _Test2() ;~ Local $123 ;# ; An inline Comment ;# EndFunc ;==>_Test2