vbman at pcpros.net
Sun Apr 16 13:27:07 EDT 2000
Yep found that one out last night. In QT the only way to trap mouse methods for
a widget is to decend a custom control of a particular type. So for say a
button I have to create a LButton of type QButton and then overide the mouse
virtual event handler. I will connect this to a slot that does the call back to
the event handler.
On Sun, 16 Apr 2000, Shane Miller wrote:
> 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.
> Shane Miller
> 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.
> > Cliff
> > _________________________________________________________________
> > To unsubscribe: mail lazarus-request at miraclec.com with
> > "unsubscribe" as the Subject
> > archives at http://www.miraclec.com/list_archives/lazarus
> 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