> The least significant bit of the return value should be ON if the > mouse button was just pressed down, but PowerPro causes it to be off > all the time. > The docs say getasynckeystate lowest bit depends on change since last call of getasynckeystate (and as per below, this is from any process)
PowerPro uses getasynckeystate extensively internally and it is possible that it will call this function as part of processing any hot key. The high bit is set appropriate in my tests. Here is more from the remarks section of the web help on asynckeystate: Although the least significant bit of the return value indicates whether the key has been pressed since the last query, due to the pre- emptive multitasking nature of Windows, another application can call GetAsyncKeyState and receive the "recently pressed" bit instead of your application. The behavior of the least significant bit of the return value is retained strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and should not be relied upon.
