🚀 go-pugleaf

"CapStick" <lol@ljones81.fsnet.co.uk> wrote in message
news:3e98910e$1@newsgroups.borland.com...

> I am able to identify and get action from
> each control from its id

WM_COMMAND itself does not indicate mouse clicks.  In order to use
WM_COMMAND for anything meaningful, you must test it for specify
notification codes in the HIWORD(lParam).  You do not show your code doing
that at all.

However, as I said earlier, mouse clicks specifically do not use WM_COMMAND
to begin with, thus you are testing for the wrong message to begin with.
Not only that, but WM_COMMAND is sent to a given window's parent, not to the
window itself directly.  Unlike mouse messages such as WM_LBUTTONDBLCLICK,
which is sent to the window directly.  That is the message you should be
using for what you're asking for.  You're not currently doing that at all

> Am i missing the point here should i be carrying out
> some sort of hit test with mouse parameters

No, you should be using completely different messages to begin with.
WM_COMMAND is not the correct message to use for this situation.

> Because Just Putting
> case WM_LBUTTONDBLCLK
> is only recognised if i double click in
>  main window client area
> Not if i doubleclick in child windows

Correct, because it appears that you are catching messages on the main
window level, and WM_LBUTTONDBLCLICK messages are sent to the actual window
clicked on, not the parent window as with WM_COMMAND.  To catch the message
for a particular child window, you would have to catch the message at the
child window level instead.

> i only need one of my controls to accept a double click

All the more reason to use WM_LBUTTONDBLBLICK on the child window level
instead.  Subclass that particular child window directly, then you can
intercept WM_LBUTTONDBLBLICK directly for that child window itself.


Gambit