Am 19.10.2010 05:49, schrieb Graeme Gill:
Florian Höch wrote:Thanks for having looked into it. Later this week, I will try to reproduce the issue on another Win7 64 system and figure out what's the difference to my system. Maybe that will yield the missing puzzle piece.Hi, I've managed to reproduce the problem. To do so, I have to have both KatMouse running, and also have the Task Manager running. Interestingly, task manager show a status of "Not responding" for dispwin when WM_PAINT messages stop appearing, so it appears that something is wedging the application message queue. Other observations are that messages come through for a while if the KatMouse property dialog is opened, and that adding dispwin.exe as an application and setting it to "Don't handle window at all" fails to prevent the problem. I'll investigate further, to see if I can figure out what's actually going on....
Wow :) Yes, I actually had the Task Manager running (minimized to the tray) as I'm in the habit of using it to monitor the CPU usage. After closing it I can run dispwin et al without issues even with KatMouse active, just like you could.
[ As a side note, I also couldn't get KatMouse's "Don't handle window at all" to work with anything (tried explorer.exe and cmd.exe to see if it just didn't work with dispwin), I think it may be a bug in KatMouse ]
Thanks again! Regards -- Florian Höch