•  Back 
  •  wind_set 
  •  Index 
  •  Tree View 
  •  Cross references 
  •  Help page 
  •  Show info about hypertext 
  •  View a new file 
Topic       : TOS - das Betriebssystem
Author      : 
Version     : tos.hyp (5. März 2013)
Subject     : Programmieren/Atari
Nodes       : 3001
Index Size  : 93602
HCP-Version : 5
Compiled on : Atari
@charset    : atarist
@lang       : 
@default    : Titel
@help       : 
@options    : +g -i -s +x +zz -t4
@width      : 70
View Ref-File8.9.11.3  WF_TOPMOST, wind_set                                     TOS

A class of windows that will always 'float' ontop of classical 
windows. One key feature of windows in any WF_TOPMOST state is that 
they do not disturb current keyboard focus, and can be used to issue 
important messages, status raports, etc., without demanding user 
interaction.

wind_set (wi_shandle, WF_TOPMOST, wi_sw1,...)

WF_TOPMOST (232)

 wi_sw1 =
           0 = Remove topmost state on the corresponding window.
           1 = Set topmost state on the corresponding window.
           2 = Set topmost state and link window visibility to the 
               owner's focus. That is, when owner is untopped the 
               window disappears, when owner regains focus, the window 
               automatically reappears.

Some common characteristics of windows with any WF_TOPMOST state set;

  1. Changing the WF_TOPMOST state can be done on open windows, but it 
     is prefer not if possible.
  2. Windows which have TOPMOST state 1 or 2 never get keyboard focus.
  3. Windows which have TOPMOST state 1 or 2 never get WM_TOPPED or 
     WM_UNTOPPED AES messages.

State 1:
Setting state 1 will make the corresponding window 'float' ontop of 
all other classical windows. State 1 windows will stay ontop until 
closed by the user or the application itself.

State 2:
Setting state 1 will make the corresponding window act like windows 
with state 1 set, with one important exception; The window is linked 
to the window owner's focus status. This means that when the 
application that owns the window looses focus, state 2 windows are 
automatically made unvisible by the AES. When the application regains 
focus, the window is automatically made visible again. This is done 
automatically, and no application handling is necessary.