At 1:27 PM -0400 5/31/02, Brian Smith wrote: >On Fri, 31 May 2002, Ken Krugler wrote: > >> >The question is how is a custom font undefined? Is it just a matter of >> >calling FntDefineFont with the same font ID and a NULL fontP, >> >> This used to be the recommended technique, but a bug in 4.0 causes a >> NULL pointer reference warning in Poser. Which reminds me, I need to >> tell Keith & the doc writer about that. > >If they're keeping an eye on the list today, you probably just did :-)
I've seen the thread here (I don't know who the doc writer is, but I don't think they monitor these lists that closely), but I'm not too sure what to do about it. I could squelch the NULL access error, but it's not clear to me that silently letting the function access NULL is OK. FntDefineFont is testing a value; I have no idea what's at NULL or which way the test will go. I don't even know if the test will change from device to device, since the contents of NULL are undefined. Therefore, it's not clear to me that silently letting it access NULL is what we want. -- Keith Rollin -- Palm OS Emulator engineer -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
