Mouse click trouble!!!

Yeah in LRESULT CALLBACK WndProc add these case statements:

case WM_LBUTTONDOWN: { code to handle when left mouse button is down return 0; } case WM_RBUTTONDOWN: { code to handle when right mouse button is down return 0; } case WM_LBUTTONUP: { code to handle when left mouse button is up return 0; } case WM_RBUTTONUP: { code to handle when right mouse button is up return 0; }

If you have your thing set to catch double clicks, you won''t get the message if the user clicks very quickly. You get WM_LBUTTONDBLCLK instead. If that''s a problem, you can change the windows class style, or you can write it as:

case WM_LBUTTONDBLCLK: case WM_LBUTTONDOWN: { code to handle when left mouse button is down return 0; }

If the opposite is true, you can have those for seperate cases, and you need to set the flag CS_DBLCLKS in the style part of your window class.




Off Topic:
You know, I can make dos code look artistic, but my windows code always looks like crap. What up with that? That''s why I always hide my windows code in some file that nobody would ever look at, like ''ugly_windows_code_dont_look_at_it_or_you_will_die_and_i_cant_be_held_responsible.yuck''

and then my make entry part of my program into something like this:

--main.cpp--
#include "ugly_windows_code_dont_look_at_it_or_you_will_die_and_i_cant_be_held_responsible.yuck"
--End of main.cpp--

Which is much nicer to look at, and it adds a sense of mystery to the debugging process.