jim@athsys.uucp (Jim Becker) (11/17/88)
In the event that the user iconifies a transient window that is part of a running process, how does one programmatically deiconify the icon or remove the icon when I wish the temporary window to disappear. How can I get this functionality working? The situation is simply this: 1) Program puts up "Alert" type window for a period of time. 2) User iconifies the Alert window during this time. 3) Programmatic Unmap of Alert doesn't affect Alert icon. 4) Next instance of the Alert window map need already has this window in iconic state, hence user never sees the content of the window, or the message(s) within. 5) Deiconification of unmapped window's icon makes the Alert window appear then vanish (since it was unmapped since the iconification took place). I haven't seen anything past hints for the initial window state (ie - normal vs. iconic) in what I have read. Can someone direct me to written material covering this, or some other direction for a solution? I would assume that the window manager is unknown, although in this case we are using uwm. -Jim Becker
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/17/88)
In the event that the user iconifies a transient window that is part of a running process, how does one programmatically deiconify the icon or remove the icon when I wish the temporary window to disappear. How can I get this functionality working? This is just one of many issues being addressed right now in the X Consortium subgroup working on a standard conventions document (ICCCM). The current proposal for this situation involves the client doing both an Unmap and sending a synthetic UnmapNotify to the window manager (but don't be surprised if existing window managers don't work with this). The subgroup is working hard to stabilize the conventions as fast as possible, and we expect to circulate the conventions for public review in the not-too-distant future.