AutoIt v3.3.9.21 Beta

[jchd]

IIRC empty arrays could only be created as returns from certain object's methods.

[BrewManNH]

I knew it was something technical that I didn't understand at the time I read it, just couldn't recall what. Either way, empty arrays aren't anything new, and old code usually never took them into account. You either had an array or you didn't, most didn't notice there were no actual elements in them.

[FaridAgl]

Example 2 of GUICtrlCreateEdit gives the following error with 3.3.9.21:

  Quote

 

"C:\Program Files\AutoIt3\Beta\ExamplesHelpfileGUICtrlCreateEdit[2].au3" (37) : ==> Only Object-type variables allowed in a "With" statement.:

With $oRP

With ^ ERROR

 

 

Also this 2 error messages from the error handler:

  Quote

 

We intercepted a COM Error !

 

err.description is:

err.windescription: Invalid class string

 

err.number is: 800401F3

err.lastdllerror is: 0

err.scriptline is: 23

err.source is:

err.helpfile is:

err.helpcontext is:

 

  Quote

 

We intercepted a COM Error !

 

err.description is:

err.windescription: Unspecified error

 

err.number is: 80004005

err.lastdllerror is: 0

err.scriptline is: 34

err.source is:

err.helpfile is:

err.helpcontext is:

 

Windows 7 Ultimate - 32 bit

[funkey]

For me it's the same, but with 3.3.8.1. So beta version has nothing to do with it.

Edit: From example file: "Needs: MSCOMCT2.OCX in system32 but it's probably already there"

Edited October 29, 2013 by funkey

[mLipok]

@D4RKON3  and   @funkey

check out this Track ticket: #2476

[FaridAgl]

@mlipok

Thanks.

[FaridAgl]

Is it a bug?

ConsoleWrite(Int("0xDEADBEAF") & @CRLF) ;Outputs -559038801 but it should be 3735928559

[mLipok]

try to use

ConsoleWrite(BinaryToString('0xDEADBEAF') & @CRLF)

or you mean something else ?

Edited November 2, 2013 by mlipok

[Jos]

  On 11/2/2013 at 9:37 PM, mlipok said:

 

try to use

ConsolewWrite(BinaryToString'(0xDEADBEAF'))

That doesn't look right to me.

[mLipok]

  On 11/2/2013 at 9:39 PM, Jos said:

That doesn't look right to me.

 

I correct my self

 

  On 11/2/2013 at 9:32 PM, D4RKON3 said:

 

Is it a bug?

ConsoleWrite(Int("0xDEADBEAF") & @CRLF) ;Outputs -559038801 but it should be 3735928559

 

ConsoleWrite(HEX('3735928559') & @CRLF)
ConsoleWrite(Dec('DEADBEEF') & @CRLF)
ConsoleWrite(Dec('DEADBEAF') & @CRLF)

from doc:

"

Default behavior is that the input string is treated as an integer. In this case, if the result is within range of a 32bit integer then it's returned as a 32bit integer, otherwise it's returned as a 64bit integer - both signed.

"

Edited November 2, 2013 by mlipok

[DXRW4E]

it seems a bug, however wants another 0 (0x0* NOT 0x*)

 

ConsoleWrite(Int("0x0DEADBEEF") & @CRLF) ;Outputs 3735928559

 

Ciao.

Edited November 2, 2013 by DXRW4E

[FaridAgl]

I just don't know if it's how it's suppose to be or not, that's why I asked "Is it a bug?".

GUICreate("")
GUISetState()

ConsoleWrite(GUIGetStyle()[0] & @CRLF) ;Output: -1798701056
ConsoleWrite(Hex(GUIGetStyle()[0]) & @CRLF) ;Output: 94CA0000

;Using calculator in windows and converting 94CA0000 from hex to decimal gives: 2496266240
ConsoleWrite(VarGetType(2496266240) & @CRLF) ;Output: Int64

[DXRW4E]

  On 11/2/2013 at 10:12 PM, D4RKON3 said:

 

I just don't know if it's how it's suppose to be or not, that's why I asked "Is it a bug?".

GUICreate("")
GUISetState()

ConsoleWrite(GUIGetStyle()[0] & @CRLF) ;Output: -1798701056
ConsoleWrite(Hex(GUIGetStyle()[0]) & @CRLF) ;Output: 94CA0000

;Using calculator in windows and converting 94CA0000 from hex to decimal gives: 2496266240
ConsoleWrite(VarGetType(2496266240) & @CRLF) ;Output: Int64 

 

always much safer to use Number(), here the correct way  in this case

ConsoleWrite(Number("0xDEADBEEF", 3) & @CRLF) ;Outputs 3735928559 

Ciao.

Edited November 2, 2013 by DXRW4E

[mLipok]

32 bit Int  

have limitation

from −2 147 483 648  to +2 147 483 647 

this is 32 bit Signed Integer

ConsoleWrite(Int("0xDEADBEEF") & @CRLF) 

From Int doc:

  Quote

 

Default = the result is auto-sized integer. See remarks.

Default behavior is that if the result is within range of 32bit integer then 32bit integer is returned. If not, 64bit integer is returned. Both signed.

 

 

This is 64 bit Signed Integer

ConsoleWrite(Int("0x0DEADBEEF") & @CRLF)

Edited November 2, 2013 by mlipok

[DXRW4E]

  On 11/2/2013 at 10:22 PM, mlipok said:

This is 64 bit Signed Integer

ConsoleWrite(Int("0x0DEADBEEF") & @CRLF)

 

ConsoleWrite(Hex(3735928559) & @CRLF) ;Outputs 00000000DEADBEEF seems to know it as 64bit
ConsoleWrite(Hex(2147483648) & @CRLF) ;Outputs 0000000080000000 seems to know it as 64bit
ConsoleWrite(Hex(1073741824) & @CRLF) ;Outputs 40000000

Ciao.

[mLipok]

  On 11/2/2013 at 10:02 PM, DXRW4E said:

ConsoleWrite(Int("0x0DEADBEEF") & @CRLF) ;Outputs 3735928559

 

When You add 0 to DEADBEEF this number change from 32 bit signed Integer to 64 bit singed integer

  On 11/2/2013 at 10:29 PM, DXRW4E said:

ConsoleWrite(Hex(3735928559) & @CRLF) ;Outputs 00000000DEADBEEF seems to know it as 64bit
ConsoleWrite(Hex(2147483648) & @CRLF) ;Outputs 0000000080000000 seems to know it as 64bit
ConsoleWrite(Hex(1073741824) & @CRLF) ;Outputs 40000000

 

So once again:

ConsoleWrite(Hex(3735928559) & @CRLF) ;Outputs 00000000DEADBEEF seems to know it as 64bit
ConsoleWrite(Hex(2147483648) & @CRLF) ;Outputs 0000000080000000 seems to know it as 64bit
ConsoleWrite(Hex(2147483647) & @CRLF) ;Outputs 7FFFFFFF seems to know it as 32bit with + Sign
ConsoleWrite(Dec('80000000') & @CRLF) ;Outputs -2147483648 seems to know it as 32bit with - Sign
ConsoleWrite(Hex(1073741824) & @CRLF) ;Outputs 40000000

ConsoleWrite(HEX(3735928559) & @CRLF) ;Outputs 00000000DEADBEEF AutoIt know it as 64bit
ConsoleWrite(HEX(-559038801) & @CRLF) ;Outputs DEADBEAF AutoIt know it as 32bit
 

Taking into account all of the above it can be concluded that in this case:

00000000DEADBEEF = 0DEADBEEF <> DEADBEEF

because

Int() Default behavior treats these above numbers in that way:

64bit = 64bit <> 32bit

 

ps.

and for that I think all is OK

but maybe someone from the group of developers, explain the matter better.

Edited November 2, 2013 by mlipok

[DXRW4E]

I think we're going offtopic, however here http://msdn.microsoft.com/en-us/library/windows/desktop/aa383751%28v=vs.85%29.aspx#INT32

2147483647           - Hex = 7FFFFFFF           Bin = 1111111111111111111111111111111    ;BinaryLen 31
2147483648           - Hex = 80000000           Bin = 10000000000000000000000000000000   ;BinaryLen 32
9223372036854775807  - Hex = 7FFFFFFFFFFFFFFF   Bin = 111111111111111111111111111111111111111111111111111111111111111  ;BinaryLen 63
ect ect ect

Ciao.

Edited November 2, 2013 by DXRW4E

[mLipok]

  On 11/2/2013 at 11:06 PM, DXRW4E said:

I think we're going offtopic, however here http://msdn.microsoft.com/en-us/library/windows/desktop/aa383751%28v=vs.85%29.aspx#INT32

2147483647           - Hex = 7FFFFFFF           Bin = 1111111111111111111111111111111    ;BinaryLen 31
2147483648           - Hex = 80000000           Bin = 10000000000000000000000000000000   ;BinaryLen 32
9223372036854775807  - Hex = 7FFFFFFFFFFFFFFF   Bin = 111111111111111111111111111111111111111111111111111111111111111  ;BinaryLen 63
ect ect ect

Ciao.

 

You are using UINT type (unsigned)

 

but AutoIt Int() function use INT type (signed)

so using INT type (signed)

its look that:

  Quote

 

2147483647           - Hex = 7FFFFFFF         Bin = 01111111111111111111111111111111 ;BinaryLen 32

-2147483648           - Hex = 80000000           Bin = 10000000000000000000000000000000 ;BinaryLen 32

Edited November 2, 2013 by mlipok

[DXRW4E]

I use Calculator (ViewProgrammer) in Windows 8.1 x64 to take the binary, UINT32 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa383751%28v=vs.85%29.aspx#UINT32

4294967295 - Hex = FFFFFFFF    Bin = 11111111111111111111111111111111    ;BinaryLen 32

the point we need to understand well such as Microsoft interprets certain things, because AutoIt (is forced) interprets them in the same way

Ciao.

Edited November 2, 2013 by DXRW4E

[jpm]

I think MS in calculator is doing something wrong when displaying in Hex 4294967295 on a qword.

If you convert the FFFFFFFF in dec dword you get back -1

If you try to paste 4294967295 to a dword you get an error

AutoIt respect as maximum what can be stored in 4 byte integer if the value cannot be stored in an int32 a int64 is used to keep the sign. The UINT32 MAX value is stored in an int64.

The only representation that cannot be stored is the MAX UINT64 as the 8-byte cannot stored the sign

Hex respect the max number of digit to use 4 or 8 bytes.

Cheers

JP