On 19 May 2014 18:39:27 +0100, Chris Young wrote: > On 19 May 2014 18:35:41 +0100, Chris Young wrote: > > > I've scoured through and can't see anything. > > Although... I think I may have fixed it. Just filtered out control > chars from the kerning, even though there shouldn't have been any > present.
Gah, I really thought that (and initialising some variables to 0) had fixed it. But it's back: (44.423848) amiga/font.c nsfont_split 345: Split 129 chars at 550px: Split at char 100 (528px) - With the problem last week, all I did with mine was force it to power off by holding the button, and (44.424815) amiga/font.c nsfont_split 365: Split 28 chars at 550px: Split at char 28 (153px) - then switch it back on again (46.156834) amiga/font.c nsfont_split 345: Split 128 chars at 550px: Split at char 100 (528px) - With the problem last week, all I did with mine was force it to power off by holding the button, and (46.157831) amiga/font.c nsfont_split 365: Split 27 chars at 550px: Split at char 27 (146px) - then switch it back on agai (47.460726) amiga/font.c nsfont_split 345: Split 129 chars at 550px: Split at char 105 (549px) - With the problem last week, all I did with mine was force it to power off by holding the button, and then (47.461570) amiga/font.c nsfont_split 365: Split 23 chars at 550px: Split at char 23 (128px) - switch it back on agaim (52.598375) amiga/font.c nsfont_split 345: Split 128 chars at 550px: Split at char 100 (528px) - With the problem last week, all I did with mine was force it to power off by holding the button, and (52.599300) amiga/font.c nsfont_split 365: Split 27 chars at 550px: Split at char 27 (146px) - then switch it back on agai I probably need to check what values I'm getting from ami_font_width_glyph to confirm if it is that. Chris
