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

[mLipok]

currently I work on:
https://github.com/WinMerge/winmerge/pull/3685

and I notice that this snippets seams to be wrongly highlighted:

#csExtra
ConsoleWrite('First test' & @CRLF)
#ceExtra

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
#csExtra
#ceExtra
#comments-endless
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

by SciTE4Au3

 

I mean line #1 open comment block and line #3 end comment block
also line #10 ends comments blocks

but Lexer does'nt change the coloring properly

as a AutoIt3.exe restults I get:
 

Quote

>"z:\AutoItPortable\App\SciTE\..\AutoIt3.exe" "Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test3.au3" /ErrorStdOut /UserParams    
Still a comment after prefix lookalikes.
>Exit code: 0    Time: 0.1012

Which means first ConsoleWrite is ommited and second ConsoleWrite is executed, which you wouldn't expect from code visualization in SciTE.

 

[mLipok]

also tidy works kinda weired:

before TIDY:

#csExtra1
ConsoleWrite('First test' & @CRLF)
#ceExtra1

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
#csExtra2
#ceExtra2
#comments-endless
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

after TIDY:

#csExtra1
ConsoleWrite('First test' & @CRLF)
#ceExtra1

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
#csExtra2
#ceExtra2
#comments-end  Extra2
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD    Extra2
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

I mean:
change 

#comments-endless

into:

#comments-end  Extra2

 

Edited October 14 by mLipok

[mLipok]

hmm... in this following case also Au3Check work not coherent with AutoIt3.exe
 

If True Then ConsoleWrite(1 & @CRLF)
#csExtra3
If True Then ConsoleWrite(2 & @CRLF)

dfadfafdadf
#ceExtra3
If True Then ConsoleWrite(3 & @CRLF)

Au3Check results:

Quote

>"z:\AutoItPortable\App\SciTE\..\AutoIt3.exe" "z:\AutoItPortable\App\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.au3" /Prod /AU3check /in "Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3"
+>23:17:31 Starting AutoIt3Wrapper (pid=27820) 25.205.1420.15 from:SciTE.exe (5.5.8.0)  Keyboard:00000415  OS:WIN_11/2009  CPU:X64 OS:X64  Environment(Language:0409)  CodePage:0  utf8.auto.check:4
+>         SciTEDir => z:\AutoItPortable\App\SciTE   UserDir => z:\AutoItPortable\App\SciTE\AutoIt3Wrapper
>Running AU3Check (3.3.18.0)  params:-d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7  from:z:\AutoItPortable\App  input:Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3
"Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3"(5,12) : error: dfadfafdadf(): undefined function.
dfadfafdadf
~~~~~~~~~~~^
Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3 - 1 error(s), 0 warning(s)
!>23:17:32 AU3Check ended. Press F4 to jump to next error. rc:2
+>23:17:32 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 0.6244
 

AutoIt3.exe results:
 

Quote

>"z:\AutoItPortable\App\SciTE\..\AutoIt3.exe" "Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3" /ErrorStdOut /UserParams    
1
3
>Exit code: 0    Time: 0.1462
 

 

Edited October 14 by mLipok

[argumentum]

46 minutes ago, mLipok said:

currently I work on:
https://github.com/WinMerge/winmerge/pull/3685

and I notice that this snippets seams to be wrongly highlighted:

#csExtra
ConsoleWrite('First test' & @CRLF)
#ceExtra

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
#csExtra
#ceExtra
#comments-endless
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

 

>Running Tidy (25.205.1420.9)  from:D:\Utilities\AutoIt3\SciTE\tidy  C:\Users\Owner\Downloads\GUIObjects\New AutoIt v3 Script Portable.au3
"C:\Users\Owner\Downloads\GUIObjects\New AutoIt v3 Script Portable.au3"(15) : ### Tidy Error: "global" is likely missing it's opening statement. next line creates a negative tablevel.
!> there were  1 error(s) encountered. look in your source for:### Tidy Error:
->17:46:39 Tidy ended. rc:1
+>17:46:39 AutoIt3Wrapper Finished.

..check your version 🤔

Edit:

 

Edited October 14 by argumentum
added image

[mLipok]

11 minutes ago, argumentum said:

..check your version

I use:
 

Quote

>Running Tidy (25.205.1420.9)  from:z:\AutoItPortable\App\SciTE\tidy  Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3
+>23:59:35 Tidy ended. rc:0
+>23:59:35 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 0.7055

 

Edited October 14 by mLipok

[argumentum]

6 minutes ago, mLipok said:

>Running Tidy (25.205.1420.9)  from:z:\AutoItPortable\App\SciTE\tidy  Z:\!!!_SVN_AU3\UDF_Forum\mLipok\Test\_TESTING\test4.au3
+>23:59:35 Tidy ended. rc:0
+>23:59:35 AutoIt3Wrapper Finished.
>Exit code: 0    Time: 0.7055
 

..same here but my screen shows

and do show an error from tidy

showing that "something is wrong" 🤷‍♂️

Edit: I think I see your point 🤔

Edited October 14 by argumentum

[Jos]

So you found a Michál special again by using a standard  🙂 

#comments-end

and bastardised that into 

#comments-endless

It is true that most utilities do a HARD test for "#comments-end" and ignore anything after that assuming it is a #comment-xxx.

So we have 2 options:

1. I dive into the Lexer/Tidy/au3stripper and test for the character following the string and check whether they are [white-space]/[lf]/[cr]
2. Don't use #comments-endxxxx

so why do you need to use it? 

 

... and when you think there's a bug i need a simple replicator script instead of having to try to figure it out from images posted. 🙂 

EDIT: I am getting the same result as @argumentum which is a wrong message about the "#comments-end" missing a start and shouldn't really be considered an error.

Edited October 15 by Jos

[Jos]

53 minutes ago, Jos said:

EDIT: I am getting the same result as @argumentum which is a wrong message about the "#comments-end" missing a start and shouldn't really be considered an error.

Made a change to avoid an error for a negative tab level for #ce/#comment-end and uploaded tidy v25.205.1420.10 to beta.

Your earlier posted script after Tidy now looks like this:
 

#csExtra1
    ConsoleWrite('First test' & @CRLF)
#ceExtra1

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
    #csExtra2
    #ceExtra2
#comments-end
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

 

Edited October 15 by Jos

[mLipok]

3 hours ago, Jos said:

So you found a Michál special again by using a standard

yeah I know:  

On 6/28/2014 at 5:33 AM, jaberwacky said:

mLipok, the master of finding bugs.

 

and yes

I'm nitpicky ... usually.

 

Edited October 15 by mLipok

[mLipok]

4 hours ago, Jos said:

so why do you need to use it? 

I do not need.
People are simply prone to making mistakes, and a stray letter can easily end up in the code.

for example:

#comments-startcomment for the CS CE block of comment
#cs Extra
#ce Extra
#comments-end   Extra

instead:

#comments-start comment for the CS CE block of comment
#cs Extra
#ce Extra
#comments-end   Extra

4 hours ago, Jos said:

and when you think there's a bug i need a simple replicator script instead of having to try to figure it out from images posted.

 

I thought everything was here:

16 hours ago, mLipok said:

before TIDY:

#csExtra1
ConsoleWrite('First test' & @CRLF)
#ceExtra1

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
#csExtra2
#ceExtra2
#comments-endless
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

after TIDY:

#csExtra1
ConsoleWrite('First test' & @CRLF)
#ceExtra1

#Region Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.
; Regression: mixed case is valid; longer names below must NOT close or open blocks.
#comments-start
#csExtra2
#ceExtra2
#comments-end  Extra2
If True Then
    ConsoleWrite("Still a comment after prefix lookalikes." & @CRLF)
EndIf
#CoMmEnTs-EnD    Extra2
Global $afterMixedCaseDirective = 2
#EndRegion Rozpoznaje dyrektywy komentarzy bez względu na wielkość liter i sprawdza granicę ich nazw.

 

 

Edited October 15 by mLipok

[mLipok]

4 hours ago, Jos said:

So you found a Michál special again by using a standard  🙂 

btw.

As I said:

16 hours ago, mLipok said:

currently I work on:
https://github.com/WinMerge/winmerge/pull/3685

I was checking the lexer for WinMerge.
Naturally (for me whent it comes with C++), I used AI (ChatGPT) for this and asked it to prepare some test .au3 scripts.
Interestingly, I first discovered the bug in WinMerge, and only then did I compare it with SciTE.

[Jos]

38 minutes ago, mLipok said:

and yes

I'm nitpicky ... usually.

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

 

[argumentum]

..never paid attention to that aspect. If there's a string after #cs, it gets duplicated on the #ce counterpart.
So if there is text after #ce and not in #cs, then is erased because what is in #cs get's duplicated/copied to #ce. 

[Jos]

1 hour ago, argumentum said:

..never paid attention to that aspect. If there's a string after #cs, it gets duplicated on the #ce counterpart.
So if there is text after #ce and not in #cs, then is erased because what is in #cs get's duplicated/copied to #ce. 

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

Edited October 15 by Jos

[mLipok]

7 hours ago, Jos said:

nobody checks them anyways

There was some one ...

I had a deperesion in the past few years so I stoped to be so nitpicky ... and became more friendly.

 

[WildByDesign]

@Jos This might not be the most appropriate place to post this request. I apologize if that is the case.

Just a small request. Could you please add DPI awareness to Tidy.exe?

I know that it consists of a file picker essentially. But I would really love for that file picker to be sharp.

Thank you for everything that you do, by the way. Your time is greatly appreciated and I am thankful that you continue to maintain so many components.

[argumentum]

..but Tidy.exe is without a GUI 🤔

[WildByDesign]

2 hours ago, argumentum said:

..but Tidy.exe is without a GUI 🤔

True. But the file selection dialog is blurry because of no DPI. If you double-click Tidy.exe, it brings up a file selection dialog to select a file to tidy. Adding DPI to the manifest of the executable would (should) show the file selection dialog with sharp DPI.

[Jos]

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.

[WildByDesign]

16 minutes ago, Jos said:

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

It 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 don't know if Tidy is written in AutoIt or not. But here is a nice function from @ioa747 which applies DPI to the process with fallback methods for older versions of Windows.

expandcollapse popup

Global Const $DPI_AWARENESS_CONTEXT_UNAWARE = -1
Global Const $DPI_AWARENESS_CONTEXT_SYSTEM_AWARE = -2
Global Const $DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE = -3
Global Const $DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2 = -4
Global Const $DPI_AWARENESS_CONTEXT_UNAWARE_GDISCALED = -5

_PM_Init()

Func _PM_Init()
    ; Prevent multiple initialization calls
    Local Static $bInitialized = False
    If $bInitialized Then Return True

    Local $bSuccess = False
    Local Const $PROCESS_PER_MONITOR_DPI_AWARE = 2
    Local $iDpiContext = 0

    ; 1. Try PerMonitorV2 (-4) - Windows 10 (Build 1703+)
    Local $aRet = DllCall("User32.dll", "bool", "SetProcessDpiAwarenessContext", "int_ptr", $DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2)
    If Not @error And $aRet[0] Then
        $bSuccess = True
        $iDpiContext = -4
    Else
        ; 2. Try PerMonitorV1 (-3) via User32.dll - Windows 10 (Build 1607+)
        $aRet = DllCall("User32.dll", "bool", "SetProcessDpiAwarenessContext", "int_ptr", $DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE)
        If Not @error And $aRet[0] Then
            $bSuccess = True
            $iDpiContext = -3
        Else
            ; 3. Try PerMonitorV1 via SHCore.dll - Windows 8.1 (Normalized to -3)
            $aRet = DllCall("SHCore.dll", "long", "SetProcessDpiAwareness", "int", $PROCESS_PER_MONITOR_DPI_AWARE)
            If Not @error And $aRet[0] = 0 Then
                $bSuccess = True
                $iDpiContext = -3
            Else
                ; 4. Fallback to SystemAware (-2) - Windows 10
                $aRet = DllCall("User32.dll", "bool", "SetProcessDpiAwarenessContext", "int_ptr", $DPI_AWARENESS_CONTEXT_SYSTEM_AWARE)
                If Not @error And $aRet[0] Then
                    $bSuccess = True
                    $iDpiContext = -2
                Else
                    ; 5. Legacy Fallback for Windows Vista / 7 / 8 (SystemAware)
                    $aRet = DllCall("User32.dll", "bool", "SetProcessDPIAware")
                    If Not @error And $aRet[0] Then
                        $bSuccess = True
                        $iDpiContext = -2
                    EndIf
                EndIf
            EndIf
        EndIf
    EndIf

    $bInitialized = True
    Return SetError(0, $iDpiContext, $bSuccess)
EndFunc   ;==>_PM_Init

17 minutes ago, Jos said:

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

Indeed, yes. The x64 version seems much faster. Especially on larger sized scripts. This is fantastic.