> > It seems that this is an issue with Cairo. configure-ing with > --enable-cairo means the input widget (actually, this affects > a lot of the widgets - for instance, the editor widget, with > cairo, runs over the boundaries of the defined area by about a > millimetre) is a little bit stuffed.
Interesting - I don't have cairo enabled in my fltk2 builds, so that'll be why I don't see the problem then I guess. Is it all versions of cairo, or just specific versions? I've seen a range of cairo-related bugs that changed with cairo version... > I'll look into this when i get the time, which should hopefully be soon. OK - but you know you are (probably) on your own out there... Fltk2 + cairo, you may be the only one actually using that configuration... Also - do you need the cairo supprt? In my testing, it was a lot slower than "native". Did look nice though. 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
