[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 8 of 9)
Previous Document: 262) Why does my SCO UIL application fail to open 60 UID files?
Next Document: 264) How can I keep track of changes to iconic/normal window state?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 8 of 9)
Previous Document: 262) Why does my SCO UIL application fail to open 60 UID files?
Next Document: 264) How can I keep track of changes to iconic/normal window state?
263) TOPIC: ICONIFICATION and DE-ICONIFICATION
Iconification/de-iconification is a co-operative process between a client and a window manager. The relevant standards are set by ICCCM. Mwm is ICCCM compliant. The toplevel (non-override-redirect) windows of an application may be in three states: WithdrawnState (neither the window nor icon visible), NormalState (the window visible) or IconicState (the icon window or pixmap visible). This information is contained in the WM_STATE property but ordinary clients are not supposed to look at that (its values have not yet been standardised). Movement between the three states is standardised by ICCCM.
Top Document: Motif FAQ (Part 8 of 9)
Previous Document: 262) Why does my SCO UIL application fail to open 60 UID files?
Next Document: 264) How can I keep track of changes to iconic/normal window state?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)
Last Update October 22 2009 @ 05:27 AM