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 My new proposals are: 1.) Change of the ANY_BUTTON value from 0x7f000000 to 0xff000000 in order to support 8 buttons instead of 7 ... this needs to be tested on Win32 and OSX too in order to avoid similar problem on those platforms (that could be currently masked with the 7f value) ... I quickly checked that and all buttons are set one by one in the bitfield in the Win32 module, but there's a 0xff mask in the OSX module ... and that could possibly cause some troubles -> needs to be analysed. 2.) Mask all unwanted bits in the set_event_xy function ... -change from: e_state = (xevent.xbutton.state << 16) | extra_state; -to: e_state = ((xevent.xbutton.state & 0x1fff) << 16) | extra_state; Of course that 0x1fff value needs to be replaced with some DEFINE 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
