Ross J. Reedstrom wrote:
[...]
> My understanding of what Guenther said was that FvwmButtons won't swallow a
> _new_ copy of a program that you already have running. Apparently, Guenther
> wants two copys of xclock, one on his button bar, one not. This is reasonable,
> and the software should allow it.
Thank you for clearifying (sp?) this. While I didn't intent to run to copies of the
xclock, I just happend to run an xclock while I was modifying my .fvwm2rc and
experienced, that the swallow command wouldn't work as expected. After finding this
bug (btw. it exsists on SunOS, X11R6 also, just installed and tested it :-), I think
that it _is_ reasonable to have two copies of a program running, one in the button
bar, and one not, although I don't intend to. What's more important, though, is that
new users probably won't spend hours to find the cause why swallow doesn't work as
expected, as I did.
Guenther
--
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 Fri Aug 30 1996 - 17:21:51 BST