I can get the option event to work just fine in my windows until I launch them from a MDI frame. Then they just don't work. I don't even see an error in the system monitor. I set it up by assigning the f2 key to the option event on the menu and when F2 is pressed sending the option event to the control with focus. What am I overlooking.

Thanks

"sending the option event to the control with focus"

How exactly are you doing this?:

Accelerator key F2

quick event Send message to @FOCUS message OPTIONS all others clear

Options event on control has action?

Steve-

Barry's response is correct.

However- you do realize that the F2 key is use to edit the toggle mode in every other windows application that your users will use? Why not use a button next to editlines, and double-click on edittables?

Mike Ruane

Mike ..

You are obviously correct with respect to Windows general usage guidelines; however, I have also used the F2 key for Options since many of my current users are AREV folks who got used to the F2 key there. This eases training during the changeover from AREV to OI for the same app.

Don Miller

C3 Inc.

Yow- I'm hardly ever 'obviously correct'

I have the F2 key on the menu setup to send the options event to the control with focus. Then on the control that has focus I have the options event setup to call a popup or index. This works just fine when I test the window by itself. However, when it is called from either the MDI parent or another window either as a MDI child or as a new window the accelerator key function seems to just disappear. I don't even see a response in the system monitor.

Mike, that sounds like an answer I would give my wife!

Steve,

Do you agree with the following?: You have a window C. Among its menu items is one with an accelerator key F2 and some quickevent - one that sends an OPTIONS message etc. You run C as a child from a MDI frame F. When C is started F's own menus get replaced by C's menus. But you get no reaction when you press F2. Nothing happens in System Monitor. Strange.

Check that F's menus at this time really have that menu item and that it says its accelerator is F2.

(Even if something made that quickevent not run the accelerator key alone should make something happen in System Monitor.)

- Oystein -

Thanks everybody…… here is the scoop

They only way that I have found to make it work has been to be sure that if the menu item on the child frame with the F2 accelerator is edit-options then it must appear on the MDI from exactly the same way. Additional you must check pass the event to the mdi frame in the menu design step. It now seems to work fine. I am not sure why and if anyone can explain to me how these different layers communicate I would appreciate it.

You all pointed out some good things and got me thinking. I appreciate the help.

Steve,

When I responded yesterday I did a test first, with a frame and child, and had no problems getting F2 to work. But I notice one difference between what I did and what you did. I leave it to you to see if it matters. I had F2 on a new menu item (in a new menu). You used the existing Edit | Options menu item.

- Oystein -

Mike ..

OK you're 'un-obviously' correct (not the same as incorrect ).

Don

View this thread on the Works forum...