Detecting a single mouse click in MFC

Question

In MFC a double-mouse click event triggers the following sequence of messages

• WM_LBUTTONDOWN
• WM_LBUTTONUP
• WM_LBUTTONDBCLK
• WM_LBUTTONUP

So responding to the WM_LBUTTONDBCLK message allows you to detect a double-click. But if I just want to detect a single-click how to I distinguish it?

But just looking at the WM_LBUTTONUP message isn't enough as it could be a single-click or it could be the first click of a double-click.

How can I successfully identify just a single-click?

Answer 1

You typically look at @MLButtonUp and you would not have single click and double click behavior on the same mouse button.

Answer 2

You could check WM_LBUTTONDOWN has not been called more than once before WM_LBUTTONUP. In practice Windows does this for you, in that if you get a WM_LBUTTONDBCLK you tend not to get a WM_LBUTTONUP.

Answer 3

You can use PreTranslateMessage() to count the messages as they appear. If you've received only the mouse messages corresponding to a single-click, and the system-configured time for double-clicking has expired, you can safely assume it's a single-click.

As far as I know there is no way to know that this is the case as it is happening, which makes sense -- until the time is expired, there's no way to know that a second click is or isn't coming.

Answer 4

that's a little tricky.

I would detect the WM_LBUTTONDOWN & WM_LBUTTONUP combo, store that event somewhere and set a timeout for a second or so. If there isn't a WM_LBUTTONDBCLK during that timeout then you have a single click.

This might imply you need to have another thread running but I think you could accomplish it with one thread.

Answer 5

I just tried this in Delphi, the behavior is the same: even when a double click is happening, a single click event is issued right after the first one of the two.

I solved it using a timer, which works like this:

• deactivate timer on WM_LBUTTONDBLCLK (and set bDbl to true)
• activate timer on WM_LBUTTONUP if bDbl==false
• deactivate on WM_LBUTTONUP if bDbl==true (and reset bDbl)

I set the interval of the timer to the time returned by GetDoubleClickTime.

MSDN says:

The GetDoubleClickTime function retrieves the current double-click time for the mouse. A double-click is a series of two clicks of the mouse button, the second occurring within a specified time after the first. The double-click time is the maximum number of milliseconds that may occur between the first and second click of a double-click.

If the timer happens to fire then you have the real click. In my case the double click interval is 500ms, so any "real click" will be delayed this long.

Answer 6

(Please allow me to call these events Mouse Up and Mouse Down. My MFC is a little rusty. And there's this stuff called .NET who's been messing up my terminology lately ;-)

Short story: You don't simply want to know about Mouse Click. You need more.

Long story:

Although this is counter-intuitive, it appears that simply wanting a mouse-click is fairly uncommon. Most often, you'll want to perform some processing on Mouse Down and do some further processing on Mouse Up. The trick is that simply tracking Mouse Up messages is not enough: Mouse Down may not have happened in your window. Do you consider it a valid click then? Especially considering that the Mouse Down processing (such as selecting an item) did not occur.

Going further up the reasoning, you should not rely on receiving a Mouse Up after you processed Mouse Down: User may have moved the mouse and released the button somewhere else (think drag'n'drop), in which case, you don't receive the MouseUp event... unless you capture the mouse on MouseDown to make sure you get mouse event up to Mouse Up even if the mouse left your window.

All in all, you end up tracking Mouse Down, capture the mouse and when you receive Mouse Up, just check if you own the capture. If not, the mouse was either double-clicked (no 2nd mouse down) or Mouse Down happened somewhere else hence you most likely don't care about this Mouse Up.

In conclusion: There's no MouseClick message simply because you wouldn't go very far with it: You need to handle more messages and implement more mechanics anyway.

Oh! And if your dealing with an existing control which already handles all this items and selection stuff, such as a listview, chances are it provides with a similar custom notification such as Item Activate or Item Selection Changed.

Answer 7

I think the solution is to start a timer after the first click & then check the elapsed time after at the next immediate click, this will tell you if it is a single click or double click.