Jos

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

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!

Correct. 🙂

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🤦)

The screenshot shows my earlier guess: 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...

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.

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

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.

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

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.

While I had the source open, I decided to make some more changes for (hopefully) better explaining what is happening and some under-the-hood optimisations. uploaded to beta. The Messages shown now look like this: In case of error: >Running Au3Stripper (25.205.1420.5) from:C:\Program Files (x86)\AutoIt3\SciTE\Au3Stripper cmdline: --- ### Inputline: 21 Outputline: 11 current FUNC:_test_a --- ### Strip Error: Unknown Func "$_lv_arfuncs[$ifunc]" used in DllCallbackRegister(). This could result removing the Func represented by this Variable C:\Development\AutoIt3\programs\test\test\testau3stripper.au3(21,1):$pPointer = DllCallbackGetPtr(DllCallbackRegister($_lv_arFuncs[$iFunc], "long", $sgPara)) --- ### Inputline: 30 Outputline: 19 current FUNC:_test_b --- ### Strip Error: Unknown Func "$_lv_arfuncs[$ifunc]" used in DllCallbackRegister(). This could result removing the Func represented by this Variable C:\Development\AutoIt3\programs\test\test\testau3stripper.au3(30,1):$pPointer = DllCallbackGetPtr(DllCallbackRegister($_lv_arFuncs[$iFunc], "long", $sgPara)) --- ### Inputline: 40 Outputline: 28 current FUNC:_test_c --- ### Strip Error: Unknown Func "$sgfunc" used in DllCallbackRegister(). This could result removing the Func represented by this Variable C:\Development\AutoIt3\programs\test\test\testau3stripper.au3(40,1):$pPointer = DllCallbackGetPtr(DllCallbackRegister($sgFunc, "long", $sgPara)) -============================================================================================================= -#### Au3Stripper Found 3 Error(s)!!!! This means your script could have problems running properly. #### -============================================================================================================= --- 0.02 Iteration 1 Strip Functions result: Output 35 lines, stripped 2 Func lines and 34 Commentlines --- 0.03 Iteration 2 Strip Variables result: Output 35 lines and stripped 0 lines +> Source 72 lines 2746 Characters. +> Stripped 2 Func/Var lines and 34 comment lines, Total 1796 Characters. +> Saved 50% lines 65% Characters. +> Au3Stripper v25.205.1420.5 finished created:C:\Development\AutoIt3\programs\test\test\testau3stripper_stripped.au3 In case they are configured to be ignored: >Running AU3Check (3.3.17.2) from:C:\Program Files (x86)\AutoIt3 input:C:\Development\AutoIt3\programs\test\test\testau3stripper.au3 +>19:03:51 AU3Check ended. rc:0 >Running Au3Stripper (25.205.1420.5) from:C:\Program Files (x86)\AutoIt3\SciTE\Au3Stripper cmdline: --- > Skipped Error Func "_test_a" Inputline: 21 Outputline: 12 Unknown Func "$_lv_arfuncs[$ifunc]" used in "DllCallbackRegister" --- > Skipped Error Func "_test_b" Inputline: 30 Outputline: 20 Unknown Func "$_lv_arfuncs[$ifunc]" used in "DllCallbackRegister" --- > Skipped Error Func "_test_c" Inputline: 40 Outputline: 29 Unknown Func "$sgfunc" used in "DllCallbackRegister" --- 0.03 Iteration 1 Strip Functions result: Output 36 lines, stripped 2 Func lines and 33 Commentlines --- > ignored 3 error(s) in UDF's defined in #Au3Stripper_Ignore_Errors_in_Funcs. --- 0.05 Iteration 2 Strip Variables result: Output 36 lines and stripped 0 lines +> Source 72 lines 2743 Characters. +> Stripped 2 Func/Var lines and 33 comment lines, Total 1732 Characters. +> Saved 48% lines 63% Characters. +> Au3Stripper v25.205.1420.5 finished created:C:\Development\AutoIt3\programs\test\test\testau3stripper_stripped.au3 +>19:03:51 Au3Stripper ended. rc:0 >Running AU3Check (3.3.17.2) from:C:\Program Files (x86)\AutoIt3 input:C:\Development\AutoIt3\programs\test\test\testau3stripper_stripped.au3 +>19:03:51 AU3Check ended. rc:0 +>19:03:51 AutoIt3Wrapper Finished.

Uploaded a changed au3stripper v25.205.1420.4 that should now work better. This will only strip FuncB #Au3Stripper_Ignore_Errors_in_Funcs=_Test_A,_Test_B,_Test_C #Au3Stripper_Ignore_Funcs=FuncA >Running Au3Stripper (25.205.1420.4) from:C:\Program Files (x86)\AutoIt3\SciTE\Au3Stripper cmdline: -> Skipped Error Func "_test_a" Inputline: 20 Outputline: 12 Unknown Func "$_lv_arfuncs[$ifunc]" used in "DllCallbackRegister" -> Skipped Error Func "_test_b" Inputline: 29 Outputline: 20 Unknown Func "$_lv_arfuncs[$ifunc]" used in "DllCallbackRegister" -> Skipped Error Func "_test_c" Inputline: 39 Outputline: 29 Unknown Func "$sgfunc" used in "DllCallbackRegister" --- 0.06 Iteration 1 Strip Functions result: Output 36 lines, stripped 2 Func lines and 17 Commentlines - ignored 3 error(s) in UDF's defined in #Au3Stripper_Ignore_Errors_in_Funcs. --- 0.08 Iteration 2 Strip Variables result: Output 36 lines and stripped 0 lines +> Source 56 lines 1519 Characters. +> Stripped 2 Func/Var lines and 17 comment lines, Total 508 Characters. +> Saved 33% lines 33% Characters. +> Au3Stripper v25.205.1420.4 finished created:C:\Development\AutoIt3\programs\test\test\testau3stripper_stripped.au3 +>21:59:26 Au3Stripper ended. rc:0

I think you actually found a bug in it as far i as I can tell. The whole "#Au3Stripper_Ignore_Errors_in_Funcs=" thing wasn't testing the Func Name where the faulty function was made from, but the Used Func name, in your case $_lv_arFuncs[$iFunc].... Hence the findings. So thanks for this detailed report, testing and replicator script. I've uploaded an update for au3stripper v25.205.1420.4 that, for this code: #Region Main #Au3Stripper_Ignore_Errors_in_Funcs=_Test_A,_Test_B,_Test_C #Au3Stripper_Ignore_Funcs=_Test_A,_Test_B,_Test_C _Test_A() _Test_B() _Test_C() wil show this now: >Running Au3Stripper (25.205.1420.4) from:C:\Program Files (x86)\AutoIt3\SciTE\Au3Stripper cmdline: ---> Skip Error for Func "_test_a" Inputline: 20 Outputline: 11 Unknown Func "$_lv_arFuncs[$iFunc]" used in "DllCallbackRegister" ---> Skip Error for Func "_test_b" Inputline: 29 Outputline: 19 Unknown Func "$_lv_arFuncs[$iFunc]" used in "DllCallbackRegister" ---> Skip Error for Func "_test_c" Inputline: 39 Outputline: 28 Unknown Func "$sgFunc" used in "DllCallbackRegister" --- 0.03 Iteration 1 Strip Functions result: Output 33 lines, stripped 4 Func lines and 18 Commentlines --- 0.03 Iteration 2 Strip Variables result: Output 33 lines and stripped 0 lines +> Source 56 lines 1539 Characters. +> Stripped 4 Func/Var lines and 18 comment lines, Total 594 Characters. +> Saved 39% lines 38% Characters. +> Au3Stripper v25.205.1420.4 finished created:C:\Development\AutoIt3\programs\test\test\testau3stripper_stripped.au3

Unless you define: #Tidy_Parameters=Skip_CE_Comment or in tidy.ini #-->Add comment to #CE/#CommentEnd and make it the same as the #CS/CommentStart Comments. ce_comment=0 Same for Func-Endfunc and #Region-#EndRegion. ... so yes I know: too many options and bad documentation, but nobody checks them anyways. 😉

Hé you know that is fine and think you did find a (minor) Tidy issue, so give the new beta a try to see whether that is better! 😉