> Okay, so if we'd look directly at the label on a higher level draw > function, then wrapping and symbol expansion would be needed, and > fl_measure() would be appropriate, but "here" in the given context > we're probably looking at broken-up strings ready to be rendered, > and then fl_text_extents() would be the better function?
Yes - good point; I'd not taken account of the fact that the string would already be formatted for output, so text_extents likely would be the better choice. Server round trips aside, of course... > Maybe there are other examples, or is it really *that* simple to > check only the x/y coordinates for "far away", and clip the > entire text then? I don't know - I was trying to think about it hard, but I think my brain melted. > What if we have coordinate transformations with a transformation > matrix? Are these basic text drawing functions located after the > transformation, and therefore in device coordinate space, or do > we have to do coordinate transformations (or at least take them > into account, if they would be done "later" by the X11 drawing > functions)? Do the transforms apply to text rendering? I thought they didn't... I do not know. I know XFT can do text transforms, but I don't think fltk has that, does it? 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 fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
