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 Yes, as I said, 1.x doesn't suffer the same problem because it handles the RELEASE method differently to the 2.x version. I've yet to get a stable-enough internet connection (not currently at home!) to check out whether or not it's a layout mask or something different, however the X man page (which is marked as current....) does seem to indicate that any value above 2^13 - 1 is an illegal - or at the very least undocumented - value for XButtonEvent::state. Although, having said all of this and proposing two solutions above, I've just realised this: Correct me if I'm wrong, but 0x7f000000 is 31 digits long (in binary, not counting leading 0s) and the highest value that X can give for an event key is 1 << 12 (which is Button5Mask), which FLTK then shifts across 16 - thus making the highest key value only 29 digits. So perhaps your fix may actually be the correct one. Yet the fact that the 1.3 dev team haven't run across similar problems with the FL_BUTTONS declaration (which is also 0x7f000000) makes me wonder..... .....Although knowing X, "feature" is right..... 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
