Posted this on the common list a week ago, but got no reply:

I have a window X where the accelerator key F2 brings up another window Y as a dialog box. F2 is handled by a menu quickevent in X. Now that other window Y has also got an F2 menu quickevent. Unfortunately that event runs too! (OI 4.0.3.)

Actually the two windows are different instances of the same MDI frame. So far I have no reason to believe the fact that X and Y are instances of the same window to be of importance. I suspect the problem has to do with the windows being MDI. To a layman (me) the problem seems similar to problems where closing or cancelling one window causes the parent window to close too. (Seen in OI 3.6.1.) See and replies from Dons Bakke & Miller.

I would appreciate a comment from Revelation on both the "old" and "new" problems.

- Oystein -

Oystein,

I want to recreate your error and in order to do so would like to know what are the parameters in your QuickEvent. I assume that you are sending the EXECUTE message to the Appname*STPROCEXEDIALOG_BOX entity. Sean </QUOTE> —- === At 12 SEP 2002 10:01AM Oystein Reigem wrote: === <QUOTE>Sean, I want to recreate your error and in order to do so would like to know what are the parameters in your QuickEvent. I assume that you are sending the EXECUTE message to the Appname*STPROCEXEDIALOG_BOX entity.[/i] F2 is the accelerator for an MDI frame menu event that runs an MDI frame commuter function with the following quickevent: - Execute a Procedure - Send Message to Entity REGIMUS*STPROCEXE@WINDOW - Parameters: 'OMNIEVENT','@SELF','DATA_ENTRY','POPUP' - Return value in Control - Property The commuter function sends a programmatic OPTIONS to the control with focus. That control is in a child with it's own commuter, which brings up the second instance Y of the frame by a call to Dialog_Box(). It's not supposed to be easy, is it? - Oystein - </QUOTE> View this thread on the Works forum...