Steve -
Thanks for the response.
Getting back to this after a long time: I tried this immediately. That's
why I need to know the position of the mouse. If I know where the mouse is
then I know which button was pushed. If it's the exit button then I can
jump out of the form. The mouse click is picked up by the exit EEP in the
active field; however, the numbers returned by ISTAT('MOUSEROW') are both
unreliable and inaccurate so I can't tell where the mouse is when the mouse
click occurs.
Bernie
--------------------------------------
At 09:01 AM 4/8/2002 -0500, you wrote:
>I might be wrong, Bernie, but I wouldn't, at this point, go so far as to say
>"proper order". I've done a pretty fair (IMO) amount of learning in this
>area in the past several weeks and I might be able to add my 2-cents worth.
>If the field "the cursor is on" is, shall we say, "active" (akin to a
>control having the current "focus"), then the FXP (Field eXit Procedure)
>would, of course, execute.
>
>Now, before anyone thinks I'm blindly apologizing f/any critique of
>RBTI/RBase, I'd probably agree w/you that it'd be nice if there were a
>"FORM-object" level way to manage whatever the current input is and what
>FORM.OBJECT invoked it. In the meantime, and I haven't read everything from
>the weekend yet, might I suggest some way of "trapping" in the FXP for just
>this thing? Now, I don't know how many form.fields you have, but could you
>possibly insert code at the top of the FXP to check for mouse input. Also,
>isn't there a new func to check for current form.object.
>
>Maybe some of this will lead to new possibilities ...
>
>... in fact, now that I've mentioned it, the func is
>"CVAL(FORM_FIELD_NAME)". It's possible that, if the mouse_click on the
>button is what would be contained in this CVAL, then it could be "trapped"
>in the 1:N other EEPs on the form. Admittedly, I haven't tested it, but, if
>it works this way, it might help me in the near future as well.
>
>Later,
>Steve in Memphis
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>> Behalf Of Bernie Corrigan
>> Sent: Sunday, April 07, 2002 1:51 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: ISTAT('MOUSEROW') not working in an EEP after a button
>> press
>>
>>
>> Karen -
>>
>> There are no stored procedures whatsoever in this system.
>> "ouserow"
>> is the truncated name of vmouserow, a valid variable.
>>
>> What I have determined is that the form handler has trouble
>> executing events in their proper order. If the cursor is on a
>> field with an
>> exit EEP and you push a button with an EEP then the field exit EEP is
>> executed before the button EEP (which may or may not be executed). I was
>> trying to pick up the mouse position so that the field exit EEP
>> would "know"
>> about the button press. Unfortunately ISTAT('MOUSEROW') does not
>> appear to
>> work right or return accurate or consistent answers. I haven't checked
>> ISTAT('MOUSECOL') because column is irrelevant to this situation.
>>
>> I have reported this as a bug to RBTI and sent them the db, code,
>> etc. so that they can replicate it. It is possible that the message is
>> issued in response to an EEP conflict situation.
>>
>> Bernie
>>
>>
>>
>>
>>
>> At 01:26 PM 4/7/2002 -0400, you wrote:
>> >Bernie:
>> >
>> >>-ERROR- Column or variable VAR STP_RETURN ouserow not found(2515)
>> >
>> >Oh man, I can't believe that you got this error message!
>> >
>> >Just yesterday, I have a form with a button that when it gets to the
>> >'closewindow' command gives the same confusing error message
>> >(only instead of the truncated 'ouserow' that you have at the end,
>> >I instead get part of the name of a variable, which is indeed
>> >found and has a value). Dumps me to the r> prompt.
>> >
>> >The first part of the error message seems to refer to a stored
>> >procedure (do you have any?). My eep can cause an action that
>> >will start a trigger, but the trigger executes perfectly every
>> >time and so does every other command in the eep.
>> >
>> >Tech Support says they don't know what that error message
>> >means. I'll be at the RBase Conference and they told us to ask
>> >Wayne what he knows about that error message. They gave me 4 tests
>> >to perform on my eep; will be doing that on Monday.
>> >
>> >
>> >Karen
>> >
>> >
>> >
>> >
>> >================================================
>> >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/
>
================================================
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/
