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 :-) > You can re-define the custom font associated with a font ID via multiple > calls to FntDefineFont, as long as you make sure the old font is no > longer used anywhere before you change it. That's what I was planning to do anyway, and you just confirmed that it's a safe move. I was going to try to unlock the previous font, though, before defining another, so that was the reason for my earlier question. Thanks for the help. I could have tried it tonight when I was going to try to implement that part of my app anyway, but just wanted to check my thinking before another headache was induced (had enough already lately with my day job). ----------------------------------------------------------------------- Brian Smith // avalon73 at arthurian dot nu // http://www.arthurian.nu/ Software Developer // Gamer // Webmaster // System Administrator "I don't want the world. I just want your half." -- TMBG -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
