On 6 Aug 2011, at 01:21, Evan Laforge wrote: > I'm happy now that I can rotate text, but it's a nicer api to use the > existing transformation framework than rather have ad-hoc parameters > to specific drawing functions. But that's a bit of a bigger task > probably, though I guess it wouldn't be so bad to support just the > rotation part until someone felt a need to implement other things like > stretching and shearing.
I have a vague recollection the "we" (i.e. somebody, not me...) looked at this and it turns out to be non-trivial. For the most part, we leverage the text rendering functions of the underlying hosts, that (in most cases) do allow for rotation of the basic string rendering. But these "host" renderers are, for the most part, entirely unaware of any transformation we may be applying. Actually, it occurs to me now that *maybe* the OSX target could support this, because of the way the display is composited and so forth, but I don't think the WinXX or XFT API's do. I am entirely likely to be wrong on all counts, of course. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
