At 11:14 AM 8/26/2002 -0700, you wrote: >[cross posted to both kyocera-forum and palm-dev-forum] > > I have a customer trying to run a piece of our software on a Kyocera > SmartPhone QCP6035, OS 3.5.3. This software uses a custom font to include > a few mathematical characters that aren't in any of the "normal" Palm > fonts, and apparently on this phone it is being changed to some other, > large font, so that fields are overflowing visually and the custom > characters aren't available. > >Is anyone aware of issues with custom fonts on this device? The >application was well tested on a whole slew of "normal" Palm devices with >OSs from 3.1 to 4.0.1 with no trouble at all.
Yes, there are severe problems on this device with custom fonts. When they define their custom fonts, they use font ID's at the beginning of the user definable range. And apparently their phone task does this even while you're app is running, so it ends up defining fonts over any that your app defined at startup. I thought licensees were given a range of custom font ID's to use, so that this problem wouldn't happen. I know Handera plays well in this respect, but the Kyocera phones don't. >Any suggestions on how to resolve this would be appreciated. Re-define your custom font every time you need to use it. That is, call FntDefineFont() immediately before you call FntSetFont(), every time. Or, use fontID's that don't conflict with the ones they use (ie, pick from the top of the user defined range instead of the bottom). -- Bill Kirby Electron Hut www.electronhut.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
