smiller at lakefield.net
Sun Apr 16 12:27:47 EDT 2000
The CLICK is caused by the WMLBUTTONUP procedure.
is csClicked is in ControlState ()meaning the mouse button was down) then
you exclude the csclicked and call CLICK.
You never pass a clicked signal, just the mouse messages.
Take a look at other product/projects of mine below!
Get paid to surf the net!
Get paid to surf the net by clicking here too!!!
Home page : http://www.lakefield.net/~smiller
Auto-IP Publisher : http://www.lakefield.net/~smiller/autoip
Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard
Lazarus : http://www.lazarus.freepascal.org
----- Original Message -----
From: "codepunk" <vbman at pcpros.net>
To: <lazarus at miraclec.com>
Sent: Sunday, April 16, 2000 12:29 AM
Subject: [lazarus] Button.OnClick
> Anyone know which LM_Message the button onclick is looking for. I am so
> close but cannot seem to get the event back to my assigned handler.
> To unsubscribe: mail lazarus-request at miraclec.com with
> "unsubscribe" as the Subject
> archives at http://www.miraclec.com/list_archives/lazarus
More information about the Lazarus