🚀 go-pugleaf

"Remy Lebeau (TeamB)" <gambit47@yahoo.com> wrote in message
news:3e987243$1@newsgroups.borland.com...
>
> "CapStick" <lol@ljones81.fsnet.co.uk> wrote in message
> news:3e9836ec@newsgroups.borland.com...
>
> > IDC EXAMPLE is a static control (child window)
> > not in a dialog box but in a main window
> >
> > which gets a reaction from one left click
>
> You're testing for WM_COMMAND, which has nothing to do with mouse clicks.
> There are separate, more specialized, messages for handling that, such as
> WM_LBUTTONDBLCLICK.  So, why not just test for that instead?
>
>
> Gambit
>
>
When testing for mouse click
By using
case WM_COMMAND:
    switch(LOWORD(wParam))
        {
 case  ID_CONTROL_1:  do this

 case   ID_CONTROL_2:  do that
I am able to identify and get action from
each control from its id

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

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
i only need one of my controls to accept a double click
Main window is set to CS_DBLCKLS
and registered with  WS_CLIPCHILDREN
USING WIN32 API free Borland Compiler




---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.463 / Virus Database: 262 - Release Date: 17/03/2003