On Tue, Aug 12, 2014 at 11:05:39PM +0100, Dominik Vogt wrote: > On Tue, Aug 12, 2014 at 04:14:56PM +0100, Thomas Adam wrote: > > FvwmConsole's socket/pipe handling is completely broken, and in moving a > > window, I'm noticing that it's being sent a tonne of broadcast packets for > > every ConfigureNotify request occuring. This floods the pipes between FVWM > > and FvwmConsole until it can be flused. > > I'm not sure I understand correctly what you say. Please confirm > or correct: > > 1. The FvwmConsole server requests events that the client is not > interested in. > > --> Can be fixed by choosing the appropriate event mask.
Fixed in CVS (when the CVS command completes; that takes ages for me). > 2. These events are not sent to the client (it cannot handle events > anyway, but only lines or text). > > 3. When a window triggers a configure notify, fvwm does many > broadcasts? > > --> If so, this _must_ be fixed in fvwm. Fixed in CVS. Fvwm generated useless broadcasts during interactive resize: * When the mouse moved without changing the window geometry. * Twice during interactive opaque resize. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
