Huw D M Davies wrote:
What's exactly the problem here? Is it lack of support of 16bit EnumFonts ?
Huw.
The problem is this line in X11DRV_EnumDeviceFonts:
if (physDev->dc->gdiFont) return FALSE;
so if the font is "MS Sans Serif", it will return 0, and old VB apps at least won't like that. But knowing the actual X11 font name given in the wine config, from the alias table it's possible to enumerate it, so those apps will start, that's what that patch does.
That's all I really managed to understand here, if there is a better way to do this I will.
On Thu, Jul 25, 2002 at 12:43:37PM -0700, Rafael Kitover wrote:
Huw D M Davies wrote:
What's exactly the problem here? Is it lack of support of 16bit EnumFonts ?
Huw.
The problem is this line in X11DRV_EnumDeviceFonts:
if (physDev->dc->gdiFont) return FALSE;
so if the font is "MS Sans Serif", it will return 0, and old VB apps at least won't like that. But knowing the actual X11 font name given in the wine config, from the alias table it's possible to enumerate it, so those apps will start, that's what that patch does.
That's all I really managed to understand here, if there is a better way to do this I will.
The alias table in the config file is used only by the old font scheme. Could you send me a relay trace of what's going on, I'd like to understand why VB apps have problems.
Thanks,
Huw.
-
Huw D M Davies -
Rafael Kitover