Custom Query (3931 matches)

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/

In the <WinAPIGdi.au3> header the definitions for BITMAPV4HEADER and BITMAPV5HEADER are incorrect.

For bV4Endpoints and bV5Endpoints, the structure lists these as an array of 3 ints. What it should be really is an array of 9 ints for both.

The relevant links which show the structures: BITMAPV4HEADER ​http://msdn.microsoft.com/en-us/library/windows/desktop/dd183380%28v=vs.85%29.aspx BITMAPV5HEADER ​http://msdn.microsoft.com/en-us/library/windows/desktop/dd183381%28v=vs.85%29.aspx

CIEXYZTRIPLE ​http://msdn.microsoft.com/en-us/library/windows/desktop/dd371833%28v=vs.85%29.aspx CIEXYZ ​http://msdn.microsoft.com/en-us/library/windows/desktop/dd371828%28v=vs.85%29.aspx FXPT2DOT30 No official link on this, but the Windows API has this defined as long in the <WinGDI.h> header:

typedef long            FXPT2DOT30, FAR *LPFXPT2DOT30;

So basically the EndPoints member type is 3 structures of 3 longs, so those arrays needs to be [9].