Re: [fltk.development] RFC: Measuring text for X11 16-bitcoordinate clipping

2012-05-09 Thread MacArthur, Ian (SELEX GALILEO, UK)
> 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_exten

Re: [fltk.development] RFC: Measuring text for X11 16-bitcoordinate clipping

2012-05-09 Thread MacArthur, Ian (SELEX GALILEO, UK)
> I believe the same goes for vertical white space as well, > ie. "\nTesting\n\n\n" and "Testing" would I think return > the same vertical size. Yes - that is what I expect/believe it does! > > fl_text_extent() does, however, give you the offset from the > string o

Re: [fltk.development] RFC: Measuring text for X11 16-bitcoordinate clipping

2012-05-08 Thread Albrecht Schlosser
Am On 08.05.2012 14:38, schrieb MacArthur, Ian (SELEX GALILEO, UK) wrote: > >> Question: How "expensive" would measuring the text before doing >> the real output in X11 be? > > I do not know. > It is likely that the correct answer will be "That depends" I guess. > > If the code is running on a loca

Re: [fltk.development] RFC: Measuring text for X11 16-bitcoordinate clipping

2012-05-08 Thread Greg Ercolano
On 05/08/12 05:38, MacArthur, Ian (SELEX GALILEO, UK) wrote: >> Second question: What function should be used: fl_measure() or >> fl_text_extents()? Would there be a performance difference to be >> expected, or would it only be the small difference in the exact >> layout? The latter could IMHO be i