I have a 12-key "keypad" 1 2 3 4 5 6 7 8 9 * 0 # where each digit is a derived class of Fl::Button and has a BMP image. The buttons are part of an Fl::Window.
When the keypad displays, it does so by calling 'show' for each of the 12 buttons in a loop. When the buttons are not supposed to be active, 'hide' is called. That is the total extent of the activity on these buttons, a for loop that executes 12 'show' calls, and another for loop that executes 12 'hide' calls. The drawing/hiding of the buttons is fine. However, the FL_PUSH/RELEASE events are (no longer) being seen by digits 2,3,8 and 9. These mouse clicks are being sent to the parent window. Actually, that's not _completely_ true... there are a small handful of pixels (near the corner of the buttons) where I can still get normal FL_PUSH/RELEASE events in the buttons themselves. I haven't figured out any pattern to these rogue pixels (that are actually working correctly). I am printing out the mouse location (from my nano-X code) and the X,Y numbers are definitely inside the range of the button locations. This wouldn't seem so strange if digits 1,4,5,6,7,*,0,9 were also mis-behaving. But they act fine. This all used to work -- I'm about to start backing out code. But any less drastic debug ideas would be appreciated. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
