>tedd wrote:
>> If you are working in PGPro, then it's not the most elegant solution, IMHO.
>> In the way that I handle the type of thing that's bugging you is to have a
>> separate FLTR file for each window. When a window is active, then the flow
>> of the program is deflected into the guts of that filter and the events are
>> done in accordance with that window's specifications. If the window isn't
>> active, then the entire filter is skipped (for the exception of the active
>> check part).
>>
>> If you are in FB, then I would simply direct all window operations into
>> case statements dealing with each specific window. In other words, for the
>> flow of the program to get to a specific routine it would require that its
>> associated window to be active.
>
>I work in the FB.
>That is indeed what I do, but I direct the event to the current output window
>rather than active window. This was the only time (in 25 appls) that I needed
>to trap the active window at this level.
>
>------------------
>Pierre A. Zippi
>------------------

Pierre:

Looks to me like you were luckly 25 times. :-)

tedd

___________________________________________________________________
<mailto:tedd@...>	               http://sperling.com/