> I think I got it. It's in src/fl_rect.cxx, line #733: > > return r ? XRectInRegion(r, x, y, w, h) : 1;
Yup - that seems likely. The x,y params are defined as int: int XRectInRegion(Region r, int x, int y, unsigned int width, unsigned int height); But I know they *used* to behave as if they were bounded at +/-32768 in the past. No idea what they are these days... It may even change from driver to driver, I suppose? The workaround from fltk-2 looks like it would be worth pursuing, I guess. SELEX Galileo Ltd 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
