AutoIt v3.3.15.5 Beta

[MarsDE]

Ah I'm sorry... had the 3.3.15.0 installed and not 3.3.15.5. The one i posted is fixed^^

[mLipok]

Please check it with 3.3.15.3 as this was a version which was released before @jpm started his "new AutoIt development route" 2 years ago.
If 3.3.15.3 is still buggy with your testing case, this will mean that @jpm fixes this bug.

[JKDos]

 

  On 2/27/2022 at 4:26 PM, Jon said:

- Added #3849: @OSVersion for Windows 11 and Server 2022.

Expand  

 

I'm sorry, but is this suppose to to say Win_11 or did I misinterpret? I get WIN_10 on a Windows 11

 

 

I can right click on the *.au3 and I have options to run/compile with beta, and it does this

 

 

 

Aside from that, how do I make SciTE use the beta version of Autoit3?  - NVM on this part, the full version of SciTE lets you do it with Alt+F5

 

Edited March 4, 2022 by JKDos

[Shark007]

@JKDos I can confirm your results.

[mLipok]

@Shark007 and @JKDos please take a look here:

https://www.autoitscript.com/trac/autoit/ticket/3849

But please do not add new request there.

Just use the following code:

; Dec, Int, Number Constants
Global Const $NUMBER_AUTO = 0
Global Const $NUMBER_32BIT = 1
Global Const $NUMBER_64BIT = 2
Global Const $NUMBER_DOUBLE = 3

Global Const $tagOSVERSIONINFO = 'struct;dword OSVersionInfoSize;dword MajorVersion;dword MinorVersion;dword BuildNumber;dword PlatformId;wchar CSDVersion[128];endstruct'

ConsoleWrite('Windows version: ' & _WinAPI_GetVersion() & @CRLF)

Func _WinAPI_GetVersion()
        Local $tOSVI = DllStructCreate($tagOSVERSIONINFO)
        DllStructSetData($tOSVI, 1, DllStructGetSize($tOSVI))

        Local $aCall = DllCall('kernel32.dll', 'bool', 'GetVersionExW', 'struct*', $tOSVI)
        If @error Or Not $aCall[0] Then Return SetError(@error, @extended, 0)

        MsgBox(0, "OSVERSIONINFO", "MajorVersion = " & DllStructGetData($tOSVI, "MajorVersion") & @CRLF & _
                        "MinorVersion = " & DllStructGetData($tOSVI, "MinorVersion") & @CRLF & _
                        "BuildNumber = " & DllStructGetData($tOSVI, "BuildNumber"))

        Return Number(DllStructGetData($tOSVI, "MajorVersion") & "." & DllStructGetData($tOSVI, "MinorVersion"), $NUMBER_DOUBLE)
EndFunc   ;==>_WinAPI_GetVersion

 

And show your's result.

 

If you take a look you will find that my results from here was:

  Quote

MajorVersion = 10
MinorVersion = 0
BuildNumber = 22000

Expand  

I must point out that I had Windows11 migrated from Windows10, and I used first officiall version which was released October 5th (last year).

I'm not able at this moment to do the same test now, but will try today.

Edited March 5, 2022 by mLipok

[Jon]

Or just type "ver" at the command prompt. Windows 11 should have a build version of 22000. That when "WIN_11" is returned from OSVersion. Pre-release of Win11 or something?

[mLipok]

,

This is from my notebook, I have access to them, but havent access to my Au3Portable (I do not like to install them).

[Jon]

  On 3/4/2022 at 11:06 AM, Musashi said:

I am aware, that any additional requests, especially in the final phase of a project, can be disturbing, if not annoying.

Would it nonetheless be possible to take a glimpse at Ticket3794 ? Some users from the German forum are waiting eagerly for a fix .

Expand  

Can you check that I've not broken RegExp with this fix?

https://www.autoitscript.com/autoit3/files/beta/autoit/AutoIt3-RegExTest.zip

[Shark007]

I like keeping it simple.
I currently use

If @OSBuild >= 22000

to detect Windows 11.

[Werty]

  On 2/27/2022 at 6:49 PM, VIP said:

Above all, I'm really looking forward to releasing the Autoit installer with full SCITE.
 

Expand  

Please no, I've tried a couple of times to use the full scite and i dont like it, i always go back to Lite, I simply cant get used to all the garble in the console that the full scite provides, Lite is fine for me

Though i'm ofcourse one the ones that rarely produces any exe files, i mostly just run my scripts from scite (lite)

[TheDcoder]

  On 3/4/2022 at 7:53 PM, Jon said:

Yes I think the bugs were all related to things like this maps inside maps, arrays inside arrays, etc.  But I also think they were unfixable due to a fundamental design flaw (in arrays as well)  😕

Expand  

Sounds like the classic reference counting bug with cyclic references. Just curious, doesn't AutoIt already have a garbage collector which can take care of these kind of memory leaks?

[mLipok]

I was able to test it with this following modified script:

#AutoIt3Wrapper_Change2CUI=y
; Dec, Int, Number Constants
Global Const $NUMBER_AUTO = 0
Global Const $NUMBER_32BIT = 1
Global Const $NUMBER_64BIT = 2
Global Const $NUMBER_DOUBLE = 3

Global Const $tagOSVERSIONINFO = "struct;dword OSVersionInfoSize;dword MajorVersion;dword MinorVersion;dword BuildNumber;dword PlatformId;wchar CSDVersion[128];endstruct"

Global $sInformation = _
        "AutoIt version: " & @AutoItVersion & @CRLF & _
        "Windows version: " & _WinAPI_GetVersion() & @CRLF & "  Build: " & @extended & @CRLF & _
        "@OSVersion: " & @OSVersion & @CRLF & _
        "@OSType: " & @OSType & @CRLF & _
        ""

ConsoleWrite($sInformation & @CRLF)
ClipPut($sInformation)

Func _WinAPI_GetVersion()
    Local $tOSVI = DllStructCreate($tagOSVERSIONINFO)
    DllStructSetData($tOSVI, 1, DllStructGetSize($tOSVI))

    Local $aCall = DllCall('kernel32.dll', 'bool', 'GetVersionExW', 'struct*', $tOSVI)
    If @error Or Not $aCall[0] Then Return SetError(@error, @extended, 0)

    MsgBox(0, "OSVERSIONINFO", "MajorVersion = " & DllStructGetData($tOSVI, "MajorVersion") & @CRLF & _
            "MinorVersion = " & DllStructGetData($tOSVI, "MinorVersion") & @CRLF & _
            "BuildNumber = " & DllStructGetData($tOSVI, "BuildNumber"))

    Return SetError(0, Number(DllStructGetData($tOSVI, "BuildNumber")), Number(DllStructGetData($tOSVI, "MajorVersion") & "." & DllStructGetData($tOSVI, "MinorVersion"), $NUMBER_DOUBLE))
EndFunc   ;==>_WinAPI_GetVersion

And I get this results:

  Quote

AutoIt version: 3.3.15.5
Windows version: 10
    Build: 22000
@OSVersion: UNKNOWN
@OSType: WIN32_NT

Expand  

[Jon]

Release candidate 1

Installer: https://www.autoitscript.com/autoit3/files/beta/autoit/autoit-v3.3.16.0-setup-rc1.exe

Zip: https://www.autoitscript.com/autoit3/files/beta/autoit/autoit-v3.3.16.0-rc1.zip

Edit: I've noticed over the last few years, and at work, it's almost impossible in modern browsers to download .exe files. So I think I'm going to wrap the installer in a .zip as well. I'll probably have two installer versions up though so it doesn't break any updater type scripts.

[AspirinJunkie]

  On 3/5/2022 at 11:02 AM, Jon said:

Can you check that I've not broken RegExp with this fix?

Expand  

The bug itself has been fixed. To illustrate the impact it had:
My JSON UDF previously took ~7 minutes to parse a 2MB JSON file into nested AutoIt types.
Now it takes 3s...

Whether generally speaking StringRegEx has not received any new bugs is difficult to say.
I don't have a comprehensive test case collection for this.
So I just tried StringRegExp with all possible options and parameters and everything worked as expected.

In short: it looks good - let's give the fix a chance.

[Musashi]

  On 3/5/2022 at 11:02 AM, Jon said:

Can you check that I've not broken RegExp with this fix?

Expand  

The fix seems to work (I used @AspirinJunkie 's script from the ticket).

EDIT : Oh, I just see that @AspirinJunkie has already replied (I had informed him about your request in the DE forum).

 

Edited March 5, 2022 by Musashi

[pixelsearch]

  On 3/5/2022 at 1:14 PM, TheDcoder said:

Just curious, doesn't AutoIt already have a garbage collector which can take care of these kind of memory leaks?

Expand  

Valik was such a character. He answered that question a few years ago in this link... in his own words. Each of his answers is something to read. One of these days I'll have to read all his answers on the Forum.

To retrieve this link, I googled "AutoIt Valik full stop", because I read his answer not so long ago and remembered the "full stop" part very well 

[Danp2]

  On 3/5/2022 at 4:00 PM, pixelsearch said:

  On 3/5/2022 at 1:14 PM, TheDcoder said:

Just curious, doesn't AutoIt already have a garbage collector which can take care of these kind of memory leaks?

Expand  

Valik was such a character.

Expand  

When I initially read this, I thought that you were stating that Valik was a garbage collector. 😆

[pixelsearch]

I didn't laugh like that for days, ty DanP2 

[argumentum]

  On 3/5/2022 at 3:00 PM, Jon said:

Release candidate 1

Expand  

 

Windows 11 version 21H2 – 10.0.22000.65 (Insider version) 22000.65    
Windows 11 version 21H2 – 10.0.22000.51 (Insider version) 22000.51    
Windows 11 version Dev  – 10.0.21996.1  (Insider version) 21996.1

..so maybe consider build 21996.x and up to be Win11 ?

[Jon]

Release Candidate 2

Reverted a reg exp fix that was causing issues. AutoIt v3.3.15.5 Beta issue with _pathsplit - AutoIt General Help and Support - AutoIt Forums (autoitscript.com)

Installer: https://www.autoitscript.com/autoit3/files/beta/autoit/autoit-v3.3.16.0-setup-rc2.exe

Zip: https://www.autoitscript.com/autoit3/files/beta/autoit/autoit-v3.3.16.0-rc2.zip