AutoIt v3.3.15.5 Beta

[Jon]

AutoIt v3.3.15.5 Beta

View File

---

3.3.15.5 (27th February, 2022) (Beta)

AutoIt:
- Added #3826: GUI "On event" While loop precision.
- Added: Doc Symbolic constants for MouseGetCursor(), GUISetCursor()  $MCID_*.
- Added #3849: @OSVersion for Windows 11 and Server 2022.

- Fixed #3836: FileExits trailing quotation mark.
- Fixed #3844: Right bracket does not register as a hotkey.
- Fixed #3830: GUICtrlSetResizing $GUI_DOCKBOTTOM fullscreen.
- Fixed #3831: GUICtrlSetPos $GUI_DOCKHCENTER.
- Fixed #2696: StringRegExp non-participating groups.
- Fixed #2866: Regread x64 remote from x86.
- Fixed #3667: empty continuation line.
- Fixed #3760: oversized Number conversion.
- Fixed #3215: GUICtrlCreateUpdown Show-Hide.

UDFs:
- Added: $ARRAYDISPLAY_NUMERICSORT for selected column for _ArrayDisplay() and _DebugArrayDisplay().
- Added: _GUICtrlEdit_SetPadding().
- Added: _WinAPI_ShellExecuteEx() Doc example.

- Fixed #3828: SetError(), SetExtended() broken doc links.
- Fixed #3827: _GUICtrlListView_ClickItem() outside listview area.
- Fixed #3835: Magic numbers in GDIPlus doc.
- Fixed #3833: _WinAPI_RegisterRawInputDevices() $iCount.
- Fixed #3842: -StringToArray() default parameter doc precision.
- Fixed #3846: missing $LVKF_* constants definition.
- Fixed #3847: _GUICtrlEdit_ShowBalloonTip() crash in _WinAPI_MultiByteToWideChar().
- Fixed #3848: _GUICtrlListView_GetItemTextArray() no error detection in multicolumn.
- Fixed #3850: _WinAPI_GetDriveNumber() does return - 1 as partition number.
- Fixed #3852: _ArrayToString() speed optimization.
- Fixed: Constants for _WinAPI_GetCursorInfo().
- Fixed: Debug.au3 when stripping.
- Fixed #3861: RunAs() doc remark.

---

• Submitter
  Jon
• Submitted
  02/27/2022
• Category
  Beta

 

[Jon]

Added more of jpm's fixes. Cheers JP.

[Musashi]

In advance : Many thanks to @Jon and the other developers like @jpm [et al.] 👍

May I dare to ask a question without appearing ungrateful or impatient : Will there be a stable version (3.3.16.0 ?) in the foreseeable future, that includes the improvements of the 3.3.15.x betas, or is it still premature ?

[Jon]

If this version is stable then I'd be looking to release it this week. Just want to get something out there as there are loadsa fixes in it.  Can worry about "improvements" at another time.

[Trong]

Thanks for your dedication, Jon.
I have 2 wishes with AutoIT.
Above all, I'm really looking forward to releasing the Autoit installer with full SCITE.
Second, if possible, when running AutoIT.exe with any name it will automatically search for the au3 or a3x script with the same name as the exe without showing the path selection dialog.

[Jos]

1 hour ago, VIP said:

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

Why?  It is available as separate installer so don't see why that would be needed. The included SciTE lite is just to get people started.

 

1 hour ago, VIP said:

Second, if possible, when running AutoIT.exe with any name it will automatically search for the au3 or a3x script with the same name as the exe without showing the path selection dialog.

Assume this is an Autoit3Wrapper request? 

Edited February 27, 2022 by Jos

[Trong]

2 hours ago, Jos said:

Why?  It is available as separate installer so don't see why that would be needed. The included SciTE lite is just to get people started.

I think 90% of users install AutoIT to script and distribute the product as binary.

The remaining 10% only need AutoIT.exe to run the script.

Therefore, only 2 versions need to be distributed.
- version 1:  includes only AutoIT.exe and AutoIT_x64.exe
- version 2: full-featured and editor.
But because AutoIT always has script_breaking_changes in versions up. When i distribution with the original code will include AutoIT.exe and AutoIT_x64.exe versions respectively.
All of the above I suggest just distributing a single full-featured version.

 

2 hours ago, Jos said:

Assume this is an Autoit3Wrapper request? 

No. Exactly 1 feature for 'AutoIT.exe' and 'AutoIT_x64.exe'

When launching 'AutoIT.exe' will search for a file with the same name as the executable (in this example the original name 'AutoIT') with precedence 'AutoIT.au3' and then 'AutoIT' .a3x', if 'AutoIT.au3' file exists in the same 'AutoIT.exe' folder then 'AutoIT.exe' will run the 'AutoIT.au3' script instead of displaying the 'Run script:' selection dialog. 

[Nine]

4 hours ago, Jon said:

If this version is stable then I'd be looking to release it this week.

That is great news.  May I say that you should remove the x64 bitwise attempt, it is full of problems (well documented previously).

[argumentum]

2 hours ago, VIP said:

No. Exactly 1 feature ...

Then say, renamed AutoIt3.exe to MyAwesomeCode.exe and it will help with the antivirus stuff and no more problems ... but it will lead to AutoIt3.exe been blocked so, nope.
Don't get me wrong. I like the idea but unfortunately will backfire. ( my 2 cents )

[Danp2]

I agree. If you need that functionality, you should be able to write your own script and compile it into an .EXE that then runs another script with a matching name.

[Trong]

3 hours ago, Danp2 said:

I agree. If you need that functionality, you should be able to write your own script and compile it into an .EXE that then runs another script with a matching name.

It needs to be done by AutoIT.exe and AutoIT_x64.exe, if you write it yourself, it's too easy and makes no sense.

[Shark007]

I'm still having problems when using

#AutoIt3Wrapper_Res_HiDpi=Y
#AutoIt3Wrapper_Res_File_Add="icons\shark.png", RT_RCDATA, shark, 0

and the dimensions of shark.png when presented in the compiled GUI.

The issue I am seeing does not exist if I eliminate HiDpi=Y or if my screen resolution is set to 100%
Since using HiDpi=Y only deals with text presentation, we are left to deal with the GUI/objects dimensions ourselves.
If my screen is set to 200% all gui/object dimensions (x,y,w,h) need to be increased by a factor of 2
I am able to distinguish that the proper x,y,w,h placement/dimensions are allocated for the pic in the Beta_GUI because I use code to change my mouse cursor when hovering the gui and its embedded objects. 

In this attached pic, the lower gui is using non beta code where the upper pic is using beta code.
These pics where taken with Windows scaling set to 225%. If I set the scaling to 100%, the pics are identical.
I have tried many things to correct this issue to no avail.

It is quite possible that ResourcesEx.au3 needs some modification but I find it odd that it works OK in the non beta release vs the beta.

 

To inform; I have moved on to using GDI+ to display PNG files in my GUI so this is no longer an issue for me.
Display of PNG files in the GUI was my only reason to use ResourcesEx.au3
I am currently using the Beta release and have no issues to report.

Edited March 1, 2022 by Shark007

[Rurorita]

The Beta Installer, upon finish, links to the Stable changelog, instead of the Beta one. The link to the Beta changelog however is on the top of the Stable changelog doc, so its not a deal.

[vince77]

On 2/28/2022 at 6:10 AM, Danp2 said:

I agree. If you need that functionality, you should be able to write your own script and compile it into an .EXE that then runs another script with a matching name.

Yes but its quite easy to do so anyway

[mLipok]

On 2/27/2022 at 11:40 PM, Nine said:

May I say that you should remove the x64 bitwise attempt, it is full of problems (well documented previously).

Please add links to this mentioned documentation.

[Nine]

1 hour ago, mLipok said:

Please add links to this mentioned documentation

Why do you delegate this search when you can do it yourself ?  Sorry to say, but as long as Jon doesn't ask me, I am not going to do it for you.

[mLipok]

What I mean by this is that it is good practice to include a link to the problem you are pointing to.
And since you know where the problem is, you probably know where it is described.
I just wanted to have a look at the problem and confirm it.

I just won't check. Because I already have a lot of other work, also related to AutoIt.

No offense, please.

Regards
mLipok

Edited March 3, 2022 by mLipok

[Jon]

Is this something that was in the last full release, jpm's alpha versions, or the beta version I just released? I don't recall touching anything to do with x64 bitwise operations in the patches I've applied for the beta. If they were broken in the last full release then I won't be messing around with them right now.

[Nine]

@Jon It is part of alpha 3.3.15.5, if you run this script, you will see the problem :

#AutoIt3Wrapper_UseX64=y
#AutoIt3Wrapper_Add_Constants=n
#AutoIt3Wrapper_Autoit3Dir=c:\Apps\Alpha\Install

#include <MsgBoxConstants.au3>

MsgBox ($MB_SYSTEMMODAL, @AutoItVersion, "Results from both calculation should be equal, but they are not")

$varA = Dec(Hex(-3, 16)) ; create int64 var
MsgBox ($MB_SYSTEMMODAL, VarGetType($varA), $varA)
$varB64 = 0xFFFFFFFFFFFFFFFF
$test = BitAND ($varA, $varB64) ; int64 vs int64
MsgBox($MB_SYSTEMMODAL, VarGetType($test), "Right result : " & Hex($test))

$varA = Dec(Hex(-3, 8))  ; create int32 var
MsgBox ($MB_SYSTEMMODAL, VarGetType($varA), $varA)
$varB64 = 0xFFFFFFFFFFFFFFFF
$test = BitAND ($varA, $varB64) ;int32 vs int64
MsgBox($MB_SYSTEMMODAL, VarGetType($test), "Wrong result : " & Hex($test))

Edit : just tested with your link to beta 3.3.15.5 and it is not included (sorry for confusion, since it was same version number)

Edited March 3, 2022 by Nine

[HurleyShanabarger]

Works fine here for me, both in 3.3.14.5 and 3.3.15.5 beta.

Edit: After the reload, I saw you edit

Edited March 3, 2022 by HurleyShanabarger