And as I've said in the fvwm-workers mailing-list:
Concerning the bug 1393 (corresponding to bug 263945 in Debian),
it seems to be due to a wrong skip value for the buttons. Consider
the following part of the modules/FvwmWinList/ButtonArray.c code:
Button *ButtonNew(char *title, FvwmPicture *p,
Hi,
The problem still occurs with fvwm 2.5.16-1.
I've attached a small .fvwm2rc file with which I could reproduce
the bug, and a corresponding snapshot of the FvwmWinList window.
Note: the bug isn't always reproducible, but after 3 tries, it
should have appeared...
--
Vincent Lefèvre [EMAIL
On 2005-07-09 13:03:52 -0500, Manoj Srivastava wrote:
A new version of fvwm has been uploaded to unstable. Could
you please see of this problem still exists with the new release?
Yes, it still exists with fvwm 2.5.12.0.CVS.2005.07.09.01-1 on x86.
--
Vincent Lefèvre [EMAIL PROTECTED]
Hi,
A new version of fvwm has been uploaded to unstable. Could
you please see of this problem still exists with the new release?
manoj
--
There are two problems with a major hangover. You feel like you are
going to die and you're afraid that you won't.
Manoj Srivastava
The cause of random windows may be due to incorrect titles.
I've attached 3 snapshots of the FvwmWinList.
The first one (buttons1.png) shows what I got just after starting FVWM:
* FvwmButtons
* xterm
* xterm
All of them are incorrect. Note that xterm is the initial title
of my xterms, but
5 matches
Mail list logo