In my opinion it is a clear Palm OS bug (Or whoever wrote Clock application; I found it installed on the Tungsten as part of the system.) The Clock application is able to geopardize other tasks in the described way as well. I thought that somebody from Palm could react...
What we did was simply to change the font ID. I know, it isn't a nice solution, but it works. You just have to select/guess the ID different from the ID used in Clock. Jan Slodicka ----- Original Message ----- From: "Bill Andreozzi" <[EMAIL PROTECTED]> > I had this same problem, which was really causing havoc, let me know what > you solution you run with. > As a note, I didn't do anything about it yet.. > thanks - bill > > > Hello > > > > The clock application (at least on Tungsten) has a side effect of > redefining > > existing fonts. > > > > Here is what we do: > > - load a custom font from the resources > > - call FntDefineFont( fntAppFontCustomBase, loadedFontPointer) > > - prior to any font-related function we call FntSetFont() to set the font > > and after the function is done we restore the original font > > > > When the Clock is run on top of our application the fntAppFontCustomBase > is > > redefined and since that moment we see just blank text fields. > > > > I think one solution would be to refresh the font definition in reaction > to > > winEnterEvent event, but I don't like it. Can somebody suggest a better > way? > > > > Jan Slodicka -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
