#: 18400 S12/OS9/68000 (OSK)
    07-Jul-93  23:34:21
Sb: #18398-#Kwindows
Fm: Kevin Darling 76703,4227
To: Zack Sessions 71532,1555 (X)

Hi guys!  Yup, it (Select, then Close) is a L-II legacy... but it's there for a
purpose.

The reason you have to select the original (or any other) window *before*
closing the current window path, is that otherwise WindIO would have no way of
checking to see if your process has permission to flip windows.

In other words, if your program DOES have a path to the currently displayed
window, then we know that the computer user was looking at your program's
window on purpose, and thus your program can flip windows without surprising
the user.

But if your program DOESN'T have a path to the currently displayed window, then
most likely the user isn't using your program at that moment, and it would be
(to say the least) inappropriate for WindIO to allow window flipping. So what
happens is that the window select does not take place, and it's actually a
later DWEnd (automatic or on purpose) which causes the flip you see to a
previous (ie: "random") screen.

The "wrong" method (Close, then Select) is also handy, btw.  If you select a
new window and then fork off a subprogram in it, then by closing the new path
before reselecting the original window, the new subprogram window stays as the
displayed one.  Very handy for graphic-shells, etc.

best - kevin


There is 1 Reply.