Custom Query (3917 matches)

In AutoIt, numerical values in the source code can be defined in decimal notation as well as in hexadecimal notation. In the number range 0x80000000 to 0xFFFFFFFFFF, however, the inputs are not interpreted as hexadecimal numbers but as a binary, which is coded as an Int32 number and therefore becomes a negative number.

A distinction must be made here between the number representation in hexadecimal notation, which should still be independent of the subsequent coding when defined in the source code, and the binary coding in specific data types, which only takes place later.

So if a user writes 0x90000001 in the source code, he expects to have written the decimal number 2415919105 (​see here). Instead, he receive the number -1879048191.

One solution would therefore be to always save hexadecimal values greater than 0x80000000 as Int64.

Example for clarification:

; interpreted as 32 Bit-Int
Global $a = 0x7FFFFFFF
Global $b = 0x80000000

ConsoleWrite("$a: " & $a & " (" & VarGetType($a) & ")" & @CRLF)
ConsoleWrite("$b: " & $b & " (" & VarGetType($b) & ")" & @CRLF)


; interpreted as 64 Bit-Int
Global $a = 0x07FFFFFFF
Global $b = 0x080000000

ConsoleWrite("$a: " & $a & " (" & VarGetType($a) & ")" & @CRLF)
ConsoleWrite("$b: " & $b & " (" & VarGetType($b) & ")" & @CRLF)

For a project I had to use FOLDERID_Documents I was suprised that this variable was missing from : APIShellExConstants.au3

So I have edited : APIShellExConstants.au3 to add below line 623 :

Global Const $FOLDERID_Documents = '{FDD39AD0-238F-46AF-ADB4-6C85480369C7}'

and of course it's works as expected (perfectly without any other modification !)

​https://learn.microsoft.com/en-us/windows/win32/shell/knownfolderid?redirectedfrom=MSDN

say:

FOLDERID_Documents
GUID 	{FDD39AD0-238F-46AF-ADB4-6C85480369C7}
Display Name 	Documents
Folder Type 	PERUSER
Default Path 	%USERPROFILE%\Documents
CSIDL Equivalents 	CSIDL_MYDOCUMENTS, CSIDL_PERSONAL
Legacy Display Name 	My Documents
Legacy Default Path 	%USERPROFILE%\My Documents

This quick "fix" allow to do, example:

Local $Dst = "C:\Temp\Documents"
_WinAPI_ShellSetKnownFolderPath($FOLDERID_Documents, $Set_Dst, 0, 0)

Is this quick "fix" could being added to the next AutoIT version ? Regards

I've found a problem where I don't think the wrong coordinates are coming from the pixel color functions.

I look for a red pixel on the screen and then move the mouse there. Then I make a tooltip with the coordinates and the color code. There is a difference between the two values! That's why I opened the AutoIt Windows information window. The pixels specified in the tooltip match, but the color codes do not. The red pixel you are looking for is not under the mouse cursor. Therefore there seems to be an error when returning the PixelSearch/PixelGetColor object.

#include <MsgBoxConstants.au3>
AutoItSetOption ( "PixelCoordMode" ,1)
AutoItSetOption ( "MouseCoordMode" ,1)

; Find a pure red pixel in the range 0,0, 1450,770
Local $aCoord = PixelSearch(0, 0, 1450, 770, 0xFF0000)
If Not @error Then
	MouseMove($aCoord[0],$aCoord[1])
	ToolTip("X and Y are: " & $aCoord[0] & "," & $aCoord[1], 0, 0)
EndIf
Sleep(1000)

;Check result again
Local $aCoord = MouseGetPos()
$color = PixelGetColor($aCoord[0],$aCoord[1],1) 

$sString = Hex($color,6) ; Convert the hex string back to the original string.
ToolTip("X and Y are: " & $aCoord[0] & "," & $aCoord[1] & " with color: #" & $sString, $aCoord[0]+10,$aCoord[1]+10)
Sleep(500)