Thank you very much! FldRecalculateField
died horribly on the small fonts (not all of
them, just the small ones), but just setting
the field to stdFont before setting it to 129
worked like a charm!
Still ... that's a great workaround, but
FldRecalculateField seems to be the way it
-should- be done ... and that still doesn't
work ...
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Ken Krugler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 30, 2000 8:13 PM
> To: Richard Hartman
> Cc: [EMAIL PROTECTED]
> Subject: Re: Help needed with problem caused by field size changes
>
>
> Richard,
>
> >I'm running a PIII with OS 3.3. I haven't debugged
> >this problem on POSE yet, because I'm sure it is in
> >the OS handleing of the fields and I don't know how
> >to debug into the OS code just yet.
>
> The bug is that you're always reusing font id = 129. When you call
> FldSetFont, it compares the field's current font with the passed
> font, and if they match it does nothing. Thus the line starts array
> doesn't get reallocated, and you wind up with the wrong number of
> lines (e.g. 7 versus 8) when switching from Midget to Ants, for
> example.
>
> The hack solution is to set the field's font to something like
> stdFont before calling FldSetFont, to force an appropriate update.
>
> Another approach would be to explicitly call FldRecalculateField
> after setting the font.
>
> -- Ken
>
> Ken Krugler
> TransPac Software, Inc.
> <http://www.transpac.com>
> +1 530-470-9200
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
