> showstopper: hangs - and when hung, have seen app, fvwm or x-server being > the one using cpu.
I cant get fvwm to show debug info, but when it hanges, these routines are on the (where) stack... XCheckIfEvent _XEventsQueued > I still see border/titlebar discrepancies sometimes. Affects xview clients... Open an xview window and some other window. Select the other window. Iconify it. Maximize then unmaximize the xview window. The xview window will now have parts of the border drawn active and other parts not. Titlebar will be shown inactive. Style * Colorset 3 Style * HilightColorset 4 Style * MWMBorder Style * DecorateTransient Style * BorderWidth 5, HandleWidth 5, ResizeOpaque, StartsAnyWhere, StaysPut, UseIconPosition, NoIconTitle, ClickToFocus, MaxWindowSize 100 100 Style * ClickToFocusRaisesOff # , CleverPlacement Style StickyStyle Sticky, NoButton 3, NoButton 5, NoButton 7, NoButton 9 Style Fvwm* NoTitle, Sticky, WindowListSkip Style Iexplorer IconOverride, IgnoreRestack, Icon map.xpm -- 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]
