On Thu, 15 Aug 1996 10:12:11 -0700
Achyutram Bhamidipaty <ram_at_epic.com>
wrote concerning 'Re: FVWM: strings in icons':
>
> This patch partly corrects the problem. When I start X up my .xinitrc
> file starts a bunch of xterms iconified, and after a few seconds the
> shell issues some escape sequence that changes the icon name... So in
> this case the icon name for the initially display icon is truncated. If
> I open the window and then re-inconify all is well.
Yes, this is a timing problem. Originally fvwm only calculated the
icon width when the icon was created. This was why doing a Restart
fixed the icon width. My patch causes it to be recalculated on every
Iconify (if there is no icon pixmap). The problem here is that
the window is created and the initial iconify happens before the shell
starts and issues its comands to change the icon name.
Now, perhaps someone out there with better knowledge of X than me will
tell me if I'm wrong, but there is no way for fvwm to be informed of
a change in the icon name. It must make explicit calls to XGetWMIconName().
Hmm, could one write a module (FvwmDaemon) that sat and polled
windows for a set of properties, and issued fvwm commands based upon
the results? What would the overhead be? Is it a silly late-night idea? :-)
Anyway, Ram, perhaps you could get around your problem by putting a delay
in your .xinitrc, a bit like this:
xterm -iconic &
xterm -iconic &
sleep 10 # enough time for the shells to start
fvwm # now safe to start wm and iconify windows
Ric
Richard J. Lister, Research Assistant
Neural Computing Research Group, Aston University
r.j.lister_at_aston.ac.uk
http://www.ncrg.aston.ac.uk/~listerrj/
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Aug 15 1996 - 18:51:16 BST