The most horrible interface ever
Wednesday, May 6, 2009 | Permalink
Here's one vote for Win32 API handling of cursors. Trying to squeeze a custom cursor through Windows' tight intestines and not getting screwed in the process in one way or another is easier said than done.
So you have a custom cursor and you called SetCursor() to use it. What if you want to hide it?
ShowCursor(FALSE)?
*BZZZZTT* Wrong answer!
SetCursor(NULL)?
*BZZZZTT* Wrong answer!
Correct answer:
PostMessage(hwnd, WM_SETCURSOR, (WPARAM) hwnd, HTCLIENT);
and then
case WM_SETCURSOR:
SetCursor(NULL);
return TRUE;
No, just calling SetCursor(NULL) directly doesn't work. You really need to do it in response to WM_SETCURSOR, or it won't work. Or at least doesn't take effect until you move the mouse or click. Or just wait a few seconds until Windows randomly postes a WM_SETCURSOR message to your window for absolutely no reason. What the heck, does that happen to cover up that things aren't really working under the hood?
[
7 comments |
Last comment by Humus (2009-05-11 22:21:33) ]
