DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2493 Version: 2.0-feature See, I'd be tentative to use a patch like the one you provided as a permanent fix because it's essentially providing a solution by prolonging the problem.... Whilst I'm aware that by default X only provides support for 5 buttons, I'm fairly sure that you can (somewhat) configure it to provide support for as many buttons as you need - however, by changing 0x7F000000 to 0x1F000000, the 2.0 branch is essentially railroaded into using only 5 mouse buttons (which is probably plenty for most, but depending on the application, not enough for others - for instance, you lose the ability to scroll horizontally with a mouse). I'm still searching high and low for whether or not there's a meaning in those bits on XButtonEvent::state that seem to be set under a new keymap, but at this point they can be &'d out, which is a better solution IMO..... Link: http://www.fltk.org/str.php?L2493 Version: 2.0-feature _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
