Custom Query

To the extent of my search, this issue wasn't raised before (sorry if I'm wrong).

I understand the FileInstall's "variable source" issues and I'm not touching that. I also know that AutoIt3Wrapper offers a similar feature (include the current script in the compiled package), but the extraction is somewhat more complex.

As a programmer, I believe that enhancing FileInstall to accept and empty string as "source" and to interpret that as a "placeholder" for the current file shouldn't be too complicated.

The advantages of such an approach would be to ease the file name based versioning if one wants to always include the original script in each compiled exe (the way it is now, the FileInstall() line has to be manually changed each time the script's file name changes).

This is an inconsistency in how AutoIt works with Registry data. RegWrite works fine for REG_QWORD, but RegRead won't read the same data back. Its surprising that it wasn't added when REG_QWORD write support was added. Nonetheless, its a problem that needs a solution

Sometimes ControlGetText or WinGetTitle will return characters that display as a mess of '?'s (in Console output). This is because of an issue with SendMessage with WM_GETTEXT. Windows will sometimes return ANSI strings, and return the # of bytes rather than characters. AutoIt internally assumes this is Unicode and treats it as such - so it displays incorrectly.

To overcome this problem, zero out a buffer, fill it with WM_GETTEXT, then do a simple wcslen() on the return to compare it to the length that WM_GETTEXT returns. It should be roughly half the size if it is an ANSI string (you need to take into account odd # returns here).

I wrote script code that works around this problem, see: www.autoitscript.com/forum/topic/148411-fix-for-unreadable-text-from-wingettext-controlgettext/