Uploaded a new version of the SciTE4AutoIt3.exe v21.316.1639.1

[Jos]

Done the same for au3stripper, and added the manifest, but am not sure there is any difference, as that is a console program:

• au3stripperx86.exe
• au3stripperx64.exe

[Jos]

3 minutes ago, WildByDesign said:

I don't know if Tidy is written in AutoIt

nope...  so in case the manifest needs updating, you have to provide me the correct manifest, as I have no option to test. 🙂 
Remember, it has to be a generic manifest, not a "works-for-me-in-my-situation" one. 

 

Edited October 27 by Jos

[Jos]

On 10/27/2026 at 10:43 AM, WildByDesign said:

t appears that I was wrong about the manifest bringing DPI awareness to the file selection dialog. I apologize. You would have to programmatically apply DPI to the process itself using SetProcessDpiAwarenessContext which would then apply DPI to any windows created within the same process.

I have added the SetProcessDpiAwarenessContext to Tidyx86.exe and Tidyx64.exe in the Beta download directory. See if that works for you. 🙂

 

[WildByDesign]

1 hour ago, Jos said:

I have added the SetProcessDpiAwarenessContext to Tidyx86.exe and Tidyx64.exe in the Beta download directory. See if that works for you. 🙂

This is absolutely perfect. Thank you.

I was able to confirm that the file selection dialog and Tidy cancellation MsgBox were both showing as Per-monitor V2 on my system and perfectly sharp. And since it the DPI is applied to the process, any other dialogs that Tidy may show that I am not familiar with will also be DPI aware. I really appreciate this. And the 64-bit performance boost is a bonus as well on large scripts.

[IronFine]

On 10/27/2026 at 10:22 AM, Jos said:

I have uploaded 2 versions of Tidy to Beta, with the added manifest for DPI awareness:

• Tidyx86.exe
• Tidyx64.exe

The x64 version is also new and seems a bit faster.

Pls try them and let me know if that works for you.

Hi Jos,
I am having a little issue - and it might be because the x64 Version is quite fast.
I have a script that is running against my repositories. It is reading all files into an array and launching multiple tidy-instances (one per file). Once that that is done, so additional formatting is done.

With the new version x64 version I getting sometime sources that are slighty formated different:

If Not (IsKeyword($x) = $y) Then   ->   If Not(IsKeyword($x) = $y) Then
If (A) Or (B) Then                 ->   If(A) Or(B) Then
Switch ($a & $b)                   ->   Switch($a & $b)
EnvGet("ProgramFiles")             ->   EnvGet ("ProgramFiles")

It seems that I don't have that problem when running the x86 version and also if I start each instance delayed by 100ms. Could that be a problem with the who is writing first to the tidy-temp file?
I know, that this is a very specifc problem to my usage of tidy and therefore I can't exactly provide a script to produce that right away. If you are willing to look into it, I can try to create a script to reproduce that.

[Jos]

I have no idea how this could be happening at this moment, so yeah, I would need some method to replicate it so I can debug it, as running a single test file with these lines in it is running fine in the x64 version of tidy.
It feels like the buildin keywords are seen as function...  but no clue yet why that could happen....
Do you run this batch from within SciTE or not?
Could you try running the update process of these multiple files with the below directive in them and capture the console output in a file?
..and then share the file (zipped) with me via Email?  This way I might be able to see what is going wrong.

#Tidy_Parameters=/sci 99

Will also remove the "Per-Monitor DPI Awareness V2 enabled" console line in the next version and only report a failure.

Edited Monday at 12:17 PM by Jos

[IronFine]

Thanks for taking you time.

I can't share the log-file as it of course contains next to all the usefil log messages also the code.

I am trying to get it replicated with some pseudo code, still working on that.

 

What I can share is a screenshotBut it seems that with /sci 99 in the log something is deviating:

Guessing from the screenshot: two tidy instance are accessing the keywords.tbl/macros.tbl at the same time.

If I manage to get the pseude-code running, I'll come back to you!

[Jos]

The screenshot shows my earlier guess:

20 hours ago, Jos said:

It feels like the buildin keywords are seen as function...  but no clue yet why that could happen....

When the keywords table is empty and a "(" is found after any word, the spaces are removed.
I will have a look at the code how this could be possible, but a replicator process would be nice for testing. 🙂

By the way: What is shown at the top of the generated log for the failing scripts, as that shows if the "funtions.tbl" exists?
Should be something like this:
 

0.00 Creating Tables
0.00 SciTE_File$:C:\Program Files (x86)\AutoIt3\SciTE\tidy\..\api\au3.api Exist: 1
0.00 Tidy_File$:C:\Users\jos\AppData\Local\AutoIt v3\SciTE\Tidy\au3.api Exist: 1
0.00 functions_File$:C:\Users\jos\AppData\Local\AutoIt v3\SciTE\Tidy\functions.tbl Exist: 1
0.06 CompareFileTime(&SciTE_File_Date, &Tidy_File_Date): 0
0.06 CompareFileTime(&functions_File_Date, &Tidy_File_Date): 0
0.06 Files are same date, so no need to rebuild.
0.06 Start Pre-processing File...

 

Edited Tuesday at 08:44 AM by Jos

[Jos]

I've uploaded a new Tidy v25.205.1420.12, which builds the tables from au3.api each run, instead of the caching done before, as that really doesn't save much processing time.

Give this version a try pls.

It also fixes a bug, as somebody has come up with a UDF name over 50 characters (53): _GDIPlus_StringFormatGetMeasurableCharacterRangeCount    (seriously🤦)

 

Edited Tuesday at 11:11 AM by Jos

[donnyh13]

@Jos,

I just wanted to confirm, with either 86 or 64 tidy, when I replace it in the tidy folder, I just rename to Tidy.exe, correct? Sorry for the silly question.

Best regards,

Donny

[Jos]

2 hours ago, donnyh13 said:

I just wanted to confirm, with either 86 or 64 tidy, when I replace it in the tidy folder, I just rename to Tidy.exe, correct?

Correct. 🙂

[IronFine]

I Jos, it is looking good on my end now with the new version. I'll will not try to get the script up and running to reproduce the issue.

Thank you!

[Jos]

4 minutes ago, IronFine said:

I Jos, it is looking good on my end now with the new version. I'll will not try to get the script up and running to reproduce the issue.

Thank you!

There is no need for the reproducer when the new script works. I will use this new way of reading the au3.api information going forward. 

Thanks for testing! 

[donnyh13]

Hi @Jos,

I just tried to run the latest (Nov. 3) tidy in Windows 7, and...

Quote

+>13:53:40 Starting AutoIt3Wrapper (pid=3336) 25.205.1420.8 from:SciTE.exe (5.5.8.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 Tidy (25.205.1420.12)  from:C:\Program Files (x86)\AutoIt3\Scite\tidy  C:\Users\Owner\Documents\GitHub\Au3LibreOffice\LibreOffice_Internal.au3
!>13:54:04 Tidy ended. rc:-1073741511
+>13:54:04 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 24.7130

 

The Oct 28 Tidy works though.

Best regards,

Donny

Edited Thursday at 08:02 PM by donnyh13

[Jos]

mmm   Win7 doesn't have that function...  Changed & Uploaded an update that should support Win7 aswell. (hopefully as I can't test that.) 

 

[donnyh13]

Works great, thanks Jos.

And the x64 is much faster. Thanks for that also!