🚀 go-pugleaf

In article <1993Jan26.163319.22622@novell.com> lkawecki@novell.com (Lewis Kawecki) writes:
>A window should be able to take
>the focus without coming to the foreground.  The window focus should be 
>able to be different from the foreground window.

This is already the case.  The WM_SETFOCUS message doesn't
automatically bring a window to the top.  This is simply part of some
message's default processing.  Either a WM_BUTTON1DOWN in the title
bar or the WM_SETFOCUS message's default processing.  If you handle
this message yourself and don't give it to the system, your app can
exhibit these properties as well.

If you bring yourself to the top (with a WinSetWindowPos call), you
don't automatically get focus, and if you give yourself focus (also
with WinSetWindowPos, with different parameters), you don't
automatically get sent to the top.

So, OS/2 is well equipped to handle what you ask.  The default
handlers only need minor changes.  These might even be corrected with
a message queue hook by an application program.
-- 
  |)  David Charlap          | .signature confiscated by FBI due to
 /|_  dic5340@hertz.njit.edu | an ongoing investigation into the
((|,)                        | source of these .signature virusses
 ~|~