Path: utzoo!attcan!uunet!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!usc!bbn.com!diamond.bbn.com!mlandau From: mlandau@bbn.com (Matthew Landau) Newsgroups: comp.windows.x Subject: Re: Some Help Please Message-ID: <14437@diamond.BBN.COM> Date: 15 Aug 90 17:13:22 GMT References: Sender: news@bbn.com Lines: 22 hallett@enterprise.positron.gemed.ge.com (Jeff Hallett x5163 ) writes: >1. I use xv_set(myFrame, FRAME_ICON, theIcon, 0) to change a base >frame's icon during execution (basically, there is a long computation >occurring - I set a timer to go off, change the icon with another one >and then go on). The effect I want to create is something like the >mailtool except loop between a few icons to keep the user up to date >even if the frame is iconified. However, the call to xv_set doesn't >seem to take effect once the frame has been rendered. This is a known olwm bug -- olwm doesn't notice when icon pixmaps change for a mapped window. In fact, it reads WM_HINTS only when a window comes out of Withdrawn state, so changing the hints on an already mapped window is a no-op. Note that this is perfectly permissible behavior according to the ICCCM, but it does fly in the face of what users and programmers expect. I've reported the bug to the author of olwm at Sun, and he agrees that the current behavior is a bad idea, and should be fixed in the next release. In XView 2.0, however, the window manager DOES notice changes in icon name, so if you change your icon name as well as icon pixmap, the user will at least have SOME indication of a change in program state.