Swallow rightmouse click UPCLICK so as not to effect Wait Windows?

I have a bunch of programs some of which are executed when I right
mouse click (pastes web site clippings in different fields depending
on contents of _cliptext after cleanup).

Some of my programs are not launched by the mouse but by function keys
or other programs.

Many of the programs launced by the right mouse click or OTHER means
contain wait window warning messages.

My problem is that if it is the right click of the mouse which
launches the program, the RELEASE of the right mouse button is in
effect a key press, so it will cause any wait window to vanish before
I have had a chance to read it.

As a result I have put a 2nd Wait command before my wait windows:

Wait
Wait Window "My Message"

It gets confusing though, because my procedure file is getting pretty
big with subroutines and I always have to think about whether this
particular subroutine is being called by the right mouse DOWN click or
by some other action so I can determine if I need the 2nd preceding
Wait clause to swallow the Right Mouse UpClick.

Also, on occassion there is more than one way a subroutine might be
called, one with the Right Mouse DOWN Click (in which case there will
be an UP CLICK and I need the double wait clause) or some other means.

If by other means the wait window doesn't appear till I keyboard
something because the double wait is holding things up.

IS THERE A BETTER WAY?

What about an

On Key Label Right Mouse Upclick && do nothing

or a conditional test to see if the program is in limbo (WAITING for
something) or to see if the right mouse button is DOWN or UP or
whatever?

Thanks


John "J.J." Jackson

Cyrus
Sat Mar 26 18:53:42 CST 2005

JJ wrote:
> I have a bunch of programs some of which are executed when I right
> mouse click (pastes web site clippings in different fields depending
> on contents of _cliptext after cleanup).
>
> Some of my programs are not launched by the mouse but by function keys
> or other programs.
>
> Many of the programs launced by the right mouse click or OTHER means
> contain wait window warning messages.
>
> My problem is that if it is the right click of the mouse which
> launches the program, the RELEASE of the right mouse button is in
> effect a key press, so it will cause any wait window to vanish before
> I have had a chance to read it.
>
> As a result I have put a 2nd Wait command before my wait windows:
>
> Wait
> Wait Window "My Message"
>
> It gets confusing though, because my procedure file is getting pretty
> big with subroutines and I always have to think about whether this
> particular subroutine is being called by the right mouse DOWN click or
> by some other action so I can determine if I need the 2nd preceding
> Wait clause to swallow the Right Mouse UpClick.
>
> Also, on occassion there is more than one way a subroutine might be
> called, one with the Right Mouse DOWN Click (in which case there will
> be an UP CLICK and I need the double wait clause) or some other means.
>
> If by other means the wait window doesn't appear till I keyboard
> something because the double wait is holding things up.
>
> IS THERE A BETTER WAY?
>
> What about an
>
> On Key Label Right Mouse Upclick && do nothing
>
> or a conditional test to see if the program is in limbo (WAITING for
> something) or to see if the right mouse button is DOWN or UP or
> whatever?
>
> Thanks
>
>
> John "J.J." Jackson
How about user CLEAR TYPEAHEAD on those which will clear the keyboard
buffer making the user have to press something after the routine has
been called.

--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com

Dan
Mon Mar 28 12:41:55 CST 2005

CLEAR TYPEAHEAD has *never* swallowed mouse clicks. To do that, you need
Inkey("M").

Dan

Cyrus Welch wrote:
> How about user CLEAR TYPEAHEAD on those which will clear the keyboard
> buffer making the user have to press something after the routine has
> been called.

JJ
Tue Mar 29 16:30:58 CST 2005

>CLEAR TYPEAHEAD has *never* swallowed mouse clicks. To do that, you need
>Inkey("M").

OK, so say I have a procedure

Procedure WNW && Wait window NoWait
Parameters PwMsg
? chr(7) && gets my attention
* Wait && may or may not be necessary - depends - see 1) below
Wait Window PwMsg+" " NoWait
Return


1) The first wait (commented out above) has been necessary to swallow
the rightmouse UPCLICK if calling program was kicked kicked off by
right mouse DOWN click.

If on the other hand the subroutine was executed by some other means,
it just holds things up and the Wait message doesn't even appear till
I move the mouse or make a keystroke.

WHERE DO I PUT THE INKEY()?

Should I do something like this:

Procedure WNW && Wait window NoWait
Parameters PwMsg
? chr(7) && gets my attention
If Inkey()=151
Wait
Endif
Wait Window PwMsg+" " NoWait
Return


Thanks

John "J.J." Jackson