Latest Build 6.0.1.3
I'm attempting to make my OpenDCL forms look and feel like my old VBA hybrid forms and I noticed the VBA forms used the Tahoma font. But the only font available in OpenDCL is Tahoma Bold. Mistake or by design?
VBA From:
(http://www.blackhorsedev.us//jb//vbaform.jpg)
Should be whatever you have installed on your system....
I have it....
If I open up VBAIDE it's available there. If I open OpenDCL it's not. And, it's in my C:/Windows/Fonts directory.
VBAIDE Fonts:
(http://www.blackhorsedev.us//jb//vbafonts.jpg)
OpenDCL Fonts:
(http://www.blackhorsedev.us//jb//OpenDCLfonts.jpg)
Hmm, it's listed on my Windows 7 x64 system. Which version of Windows? Does it show up in the font toolbar?
Windows XP Pro 32 bit.
It shows up everywhere else: C:/Windows/Fonts, AutoCAD, Photoshop, Illustrator, Word, etc.
It looks like it's an OpenType font per your screen shot... Maybe Win. XP/OpenDCL don't like OpenType as much as TrueType... Just a guess... :)
In C:/Windows/Fonts it's a true type. Weird.
If you right-click on the true-type font in control panel, do you have an option to 'Hide' it?
Quote from: jbuzbee on March 29, 2011, 01:05:19 PM
In C:/Windows/Fonts it's a true type. Weird.
Are you sure about that?
That's weird, I just loaded OpenDCL on my laptop - Windows XP Pro 32 bit - and the exact same thing is happening.
QuoteIf you right-click on the true-type font in control panel, do you have an option to 'Hide' it?
No
Never mind guys - thanks for the help. I went with Verdana. 8)
Browsing the forum I came across this topic and I had the same problem as jbuzbee (in my case with Windows XP Home 32 bit and ODCL 6.0.2.3).
Two solutions that work for me:
1.
In the font list select Tahoma Bold and in the text box above the list just remove " Bold".
2.
Make a backup copy of tahoma.ttf and tahomabd.ttf.
Deinstall both Tahoma and Tahoma Bold.
Windows XP should now reinstall these fonts automatically.
If that doesn't happen reinstall manually using the backup files.
Result: "Tahoma" now appears in the ODCL font list.
I think this font problem is now fixed for the next build.