Re: Display problems CPF5192 with mouse clicks

Hi Bill,

I haven't had the opportunity to use MOUBTN, but from the DDS manual

"Note: Although it is permitted, it may not be advisable to program some
combinations of pointer device events on the same mouse button and shift
state. For example, if the right button is programmed, right button double
click should not be programmed because it may not be detected due to the
keyboard being locked from the right button pressed event. Using the *QUEUE
parameter will allow the application to handle this situation."

hth,
Peter Dow
Dow Software Services, Inc.
909 793-9050 voice
909 522-3214 cellular
909 793-4480 fax

----- Original Message -----
From: "Hopkins, Bill" <BHopkins@saurerinc.com>
Sent: Friday, August 30, 2002 1:36 PM
Subject: RE: Display problems CPF5192 with mouse clicks
>  Which I had defined in first pop up window(ILOC00/ILOCW00) as (*ULP *ULD
> ENTER). When on second window(VNDR00/VNDR00W) with no MOUBTN define if you
> click around window(which does have sub file record and SFLPSD does equal
> 1). Mouse Click acted like MOUBTN from ILOC00/ILOC00W and it loop through
> code and back to EXFMT of window(VNDR00/VNDR00W). If you continued to
CLICK
> over and over it repeated same loop but it seem on FASTER clicks it would
> CPF5192 on me. Strange :(.  I change Client Access to Mouse Position on
Left
> Mouse Click and it was fixed but push buttons stopped working(of course no
> ENTER).
> But thought maybe MOUBTN from ILOC00 still on or problem in background in
> VNDR00 ???
> Set Client Access back to default value.
>
>  I then changed MOUBTN value in ILOC00/ILOC00W to (*ULD ENTER)- recompile.
> Follow same flow that gave error CPF5192. NO ERROR now. Can even see Click
> difference on VNDR00/VNDR00W. All works.
>
> Any one know WHY??? Please explain??? Conflicts between Client Access
> translate and *ULP *ULD on AS/400 screen???? And why did MOUBTN(*ULP *ULD
> ENTER) appear to still be on in VMDR00/VNDR00W,Even after ILOC00/ILOC00W
> closed *INLR???