>>>In my form class I emulate the behavior of what I've had in FPD, which
>>>reacted on F3 and F4. In the form class init, I have
>>>

>>>on key label f3 _screen.activeform.f3f4(3)
>>>on key label f4 _screen.activeform.f3f4(4)
>>>

>>
>>This works only if you have a form on screen and if that form has an F3F4
>>method.
>
>Right so. The form class has it, and...
>
>>In my opinion this shouldn't be in the form's Init, but in the main
>>program/app class Init.
>
>....the above code is also in the form class's init, otherwise I should
>have done what you suggested. Since it's all contained in the same
>class, the _screen.activeform.f3f4(4) syntax is just a workaround for
>not being able to use thisform.f3f4(4) in and OKL call (which was the
>cause of this thread).
>
>>>Maybe I should move it to form's Activate, and also dismiss in any
>>>proper place (it gets dismissed in Unload now)... which event fires if
>>>the form's window is not the active window anymore?
>>
>>If you do it as I stated above, you don't need to worry about the dismiss
>>of those settings anymore.
>
>The F3F4 procedure is tightly connected to the form class, so it doesn't
>make sense as a separate .prg or a method in the app - its natural place
>is in the form class... if ever anyone finds out what's "natural" in
>programming :)
>
>Now since I want to have it active within the life of a form class
>instance only, the dismissal should be in form.deactivate, I suppose -
>yes, I've took a look at the help, I should dismiss it there, but in
>unload also, since deactivate doesn't get triggered when the form just
>unloads. Or just put this.deactivate in unload?

It sounds like you need one method that will deactivate the on keys and call this method from all apropriate methods.

Vlad