>I have a tree view derived class in which I handle double clicks
>(NM_DBLCLK or WM_LBUTTONDBLCLK, doesn't matter which). I am supposed
>to launch a (modal) dialog box which works fine.
>
>However, if I left or right click *anywhere* on the entire screen
>(including the launched dialog box itself) that click goes to the tree
>view! Just the first click. All subsequent clicks go to the dialog box
>as they should.

Sandeep,

Try delaying when you invoke the modal dialog box.

Rather than do it in the double click handler, post a user defined
message to the same window from the double click handler, and display
the dialog in response to receiving that user defined message.

Dave
--
MVP VC++ FAQ: http://www.mvps.org/vcfaq

David Lowndes wrote in message news:...
> Try delaying when you invoke the modal dialog box.
>
> Rather than do it in the double click handler, post a user defined
> message to the same window from the double click handler, and display
> the dialog in response to receiving that user defined message.

Nope... that didn't do it (and yes, I used PostMessage() not
SendMessage()). What you said sort of makes sense though.

I do have a "workaround" : send a WM_LBUTTONDOWN/WM_LBUTTONUP before
launching the dialog which works but has other problems. The dialog
won't launch unless I _move_ the cursor.

Scary huh?

Sandeep

>Nope... that didn't do it (and yes, I used PostMessage() not
>SendMessage()). What you said sort of makes sense though.

Hmm, are you passing the double click notification on to the default
handler?

Dave
--
MVP VC++ FAQ: http://www.mvps.org/vcfaq

bogusami@hotmail.com (Sandeep Pulla) wrote in message news:...
> I do have a "workaround" : send a WM_LBUTTONDOWN/WM_LBUTTONUP before
> launching the dialog which works but has other problems. The dialog
> won't launch unless I _move_ the cursor.

OK. I have fixed this problem I believe.

// inside NM_DBLCLK handler
PostMessage(WM_LBUTTONDOWN, ...); // instead of SendMessage()
PostMessage(WM_LBUTTONUP, ...);
// launch dialog here

This works, don't ask me why.

Sandeep

Dave,

David Lowndes wrote in message news:...
> Hmm, are you passing the double click notification on to the default
> handler?

When I add a handler for NM_DBLCLK, it is an ON_NOTIFY_REFLECT handler
and there is no default (base class) handler. You do have a parameter
LRESULT* pResult which is typically set to zero/non-zero to indicate
whether or not the parent should handle the message -- I've tried both
without any apparant difference.

Thanks,
Sandeep