Jim

It's not quite accurate to say that ISTAT('Mouserow') doesn't work in R:Base
for Windows: it may not work on FORMS, but I've used it successfully with
displaying a "menu" using a graphical image file followed by a FILLIN var=0
command; a mouseclick position is successfully captured and can be used in
code.

David BLocker

----- Original Message -----
From: "Jim Blackburn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 08, 2002 12:26 PM
Subject: Re: ISTAT('MOUSEROW') not working in an EEP after a button press


> Bernie:
> The ISTAT functions for mouse location do not operate in Windows R:Base. I
have had success using:
> SET VAR vbutton text = (sget(.#FORM_COLUMNNAME,4,1))
>
> Which returns the last button pushed. The sget is necessary because it
returns a long text field with unpredictable contents.
>
> There is also:
> SET VAR vbutton = (CVAL('form_field_name'))
> but this seems to be designed for the form remaining open. I often set up
buttons to close the form then check to see which button closed it - with
that arrangement and the CVAL function, it returns the current value of
whatever form is currently open - I often have a form within a form.
>
> One of these should solve your problem.
>
> Jim Blackburn
> Kodiak
> Bernie Corrigan wrote:
> >
> >         I am attempting to pick up the position of the mouse at the time
of
> > a button press from an exit EEP attached to a from field.  The button is
> > located at about row 20 on the form yet ISTAT('MOUSEROW') returns the
value
> > 1.  The field with the EEP which uses the ISTAT function is on row 7.
When
> > I press [Esc] to leave the process I get the following error.  Note
there
> > are no stored procedures in this database system.
> >
> > -ERROR- Column or variable VAR STP_RETURN       ouserow not found(2515)
> >
> >         The reason it is necessary to pick up the mouse row position
from an
> > EEP is that when a form button is pressed the form handler processes an
exit
> > EEP (if it exists) for whatever field the cursor was in at the time of
the
> > button press before it processes the EEP associated with the button
which
> > was pressed.  If the field exit EEP checks field values for errors and
> > returns the user to the field in case of a null or erroneous value then
the
> > form user can get stuck in a loop where a button press to exit the form
will
> > simply return the user to the field the cursor was in at the time of the
> > button press.  One could get around this by picking up the mouse
position
> > from the field exit EEP and skipping error checks depending on mouse
> > position.  Unfortunately it seems that the field EEP can't get an
accurate
> > read of mouse position from the ISTAT function.
> >
> > Comments?  Ideas?
> >
> > ================================================
> > TO SEE MESSAGE POSTING GUIDELINES:
> > Send a plain text email to [EMAIL PROTECTED]
> > In the message body, put just two words: INTRO rbase-l
> > ================================================
> > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> > In the message body, put just two words: UNSUBSCRIBE rbase-l
> > ================================================
> > TO SEARCH ARCHIVES:
> > http://www.mail-archive.com/rbase-l%40sonetmail.com/
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to