🚀 go-pugleaf

jms wrote:
> I'm developing an app that happens to use a custom font. After starting a
> Tungsten T device using the select button to look at world clock then
> hitting OK my custom font is either drawn in the huge clock number
> characters or is blank, also causes occasional crashes.

That sounds like a bug to me.

> Anyone come across this? Any good workarounds? Is there a notification I
> should be looking for to reload my fonts?

Since user-interaction is controlled by events on the Palm, one
workaround is to set or save the font at some point in the app's
main event loop.  Your code has control while you're handling a
given event, so if you do that, there is no way an interloper
like the world clock could screw up the font on you.

Two ways spring to mind.  One is to FntSetFont() every time at
the top of your form's event handler (if you only use the font
in one form and if you use no other font on that form).  The
other way is to replace all calls to SysHandleEvent() with
FontPreservingSysHandleEvent():

     Boolean FontPreservingSysHandleEvent (EventType *e)
     {
         FontID savedfont;
         Boolean handled;

         savedfont = FntGetFont ();
         handled = SysHandleEvent (e);
         FntSetFont (savedfont);
         return handled;
     }

I don't, though, if these repeated calls to FntSetFont() will slow
down event handling...

   - Logan