1. WM_LBUTTON ?
- Posted by Euman <euman at bellsouth.net>
Mar 13, 2001
-
Last edited Mar 14, 2001
Hello again,
I was wondering if maybe someone would show me how to
stop a Mouse Button click, the below does not work.
This is Windows related/
while event = WM_LBUTTONDOWN do
if event = WM_LBUTTONUP then
exit
end if
--empty_stack( )
--parent = 1 child = 0 sub_child = 0
scroll_up( )
-- should scroll_up here
end while
Euman
2. Re: WM_LBUTTON ?
- Posted by leviathan at uswest.net
Mar 13, 2001
-
Last edited Mar 14, 2001
> Hello again,
>
> I was wondering if maybe someone would show me how to
> stop a Mouse Button click, the below does not work.
> This is Windows related/
>
Try looking up onMouse in the Win32Lib manual :) Perhaps that'll work? :)
(Did for me for a weird little listview issue I had - thought I'd had to
capture LV events, instead I just caught onMouse events, and only
got the dblclick I needed :))
I wonder if I ever added in that fix (Derek?) told me to throw in for
the LVs...
And I'll take this time to point out another bug.... later...
--"LEVIATHAN"
3. Re: WM_LBUTTON ?
Hi,
can you fill me in a little more?
> I was wondering if maybe someone would show me how to
> stop a Mouse Button click,
I'm guessing that there is a control that normally reacts to a mouse click
but you want it to ignore it this time. Is that right? Is that a scrollbar,
a pushbutton or what?
You could try to trap it using onEvent handler. Some types of controls don't
send all events to the application, so try this first but don't be too
surprised if fails.
--------------------
procedure eh(atom iMsg, atom wParam, atom lParam)
if find(iMsg, {WM_LBUTTONDOWN, WM_LBUTTONUP}) then
returnValue(0) -- signal we want to ignore this event.
end if
end procedure
onEvent[myControl] = routine_id("eh")
-------------------------
cheers,
Derek Parnell
Melbourne, Australia
"To finish a job quickly, go slower."
4. Re: WM_LBUTTON ?
Euman wrote:
>I was wondering if maybe someone would show me how to stop a Mouse Button
>click, the below does not work.
You should be able to use returnValue(True) to prevent the default Windows
behavior of an event from triggering.
-- David Cuny
