On Tue, Oct 22, 2002 at 12:36:02AM -0400, Chris Siebenmann wrote: > An additional two notes: > > I localized the problem to fvwm 2.4.10's fvwm/stack.c changes; the 2.4.9 > stack.c (hacked to change '->pstack' to '->stack.p') doesn't exhibit the > problem when compiled into 2.4.10. > > The problem appears to go away if I force the do_lower parameter to > fvwm/stack.c's restack_windows() to be zero. I suspect that this is > not the actual answer, but I lack the understanding of fvwm's internals > to understand what I just broke. (Everything seems to work fine for me, > but I don't use multiple layers.)
I think I got all the bugs. The stacking code is always a rich source of bugs. Within 24 hours I found no less than six, some introduced in 2.4.10 or later and some just hidden by fortunate circumstances or uncontrolled side effects in earlier versions. Expect the 2.4.13 release within a week. It would be nice if you could download the latest code from the 2.4 branch in cvs and double check wether all problems are gone: $ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs/fvwm co -r branch-2_4 -d fvwm-2.4 fvwm (this checks out the 2.4 branch into a directory fvwm-2.4). Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
