Keith Packard writes:
> Sorry, my description was of two different ways to fix having more than
> one display open at a time;
Got it. Sounds good.
> Take a look at XftPatternVaBuild, XftFontMatch and XftFontOpenPattern;
> building your own XftFontVaOpen out of those should be easy enough. I'll
> consider adding it to the next major version of Xft.
Yes, and that's exactly what XftFontOpen uses of course. So, for now,
I just have a copy-and-pasted XFtFontOpen in my library with a
different name.
To avoid the code duplication, I would prefer:
XftFont*
XftFontOpen (Display *dpy, int screen, ...)
{
va_list va;
XftFont *font;
va_start (va, screen);
font = XftFontVaOpen(dpy, screen, va);
va_end (va);
return font;
}
XftFont *
XftFontVaOpen (Display *dpy, int screen, va_list va)
{
/* All the guts exactly as currently in XftFontOpen */
}
But, that's a trivial little thing.
On a more significant scale, you've mentioned several times that you'd
like to move a large portion of the font handling code out of Xft and
into a separate non-X library. Have you started designing that much? I
think I might prefer it over Xft, since some of what Xft is doing,
(such as abstracting away the differences between core colors/fonts
and their Render/TrueType counterparts), I would like to do in my
code, but in a different way.
-Carl
--
Carl Worth
USC Information Sciences Institute [EMAIL PROTECTED]
3811 N. Fairfax Dr. #200, Arlington VA 22203 703-812-3725
_______________________________________________
Render mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/render
