Custom Query (3917 matches)

I'm not thoroughly convinced this is an AutoIt bug, it may just be a limitation of the Windows API.

GUICreate("Bug Test")
GUICtrlCreateInput("Test", 10, 10, 100, 20)
GUICtrlSetTip(-1, "This works")
GUICtrlCreateCombo("Test", 10, 10, 100, 20)
GUICtrlSetTip(-1, "This doesn't work")
GUISetState()
Do
Until GUIGetMsg() = -3
Exit

Not really a request, just a suggestion. When compiling script, the default is to use the <script name> followed by the .exe extension. I would propose a change to that for x64 compilations only. Change it to <script name> followed by _64.exe

That would make it much easier for those of us who like to write auto-compile scripts. There would be no need to do any changing of file names like there is now.

I can't really provide a meaningfull demo script for this but You can read the conversation starting from this post. ​http://www.autoitscript.com/forum/index.php?showtopic=114423&view=findpost&p=801540

I don't really think it's an AutoIt bug. It seems to be hex related and probably in PCRE.

I'm wondering if updating the engine from 8.0.0 to 8.0.2 might be the solution. I notice several bug fixes in the last 2 versions.

Also there is a docs error for the chart for StringRegExp() \x## = Match the ascii character whose code is given in hexadecimal. Can be up to 2 digits. should read either \x## = Match the ascii character whose code is given in hexadecimal. Can be up to 2 xdigits. OR \x## = Match the ascii character whose code is given in hexadecimal. Can be up to 2 characters.

None of this would ever matter if we could get Unicode support working.