> This bug exists for a long time when using FLTK 1.1.x in combination > with the unstable (when I remember correctly) branch of FVWM. > And since > FVWM stable and all other WM's I've used so far aren't > affected, I'm not > sure this really is a FLTK issue.
On the basis of Freddy's input, do we think this may be a fvwm2 bug? Does anybody know what fvwm2 does that differs from other wm's, to trigger this behaviour? Maybe it still hints at some underlying issue? SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
