I have been playing around with various ideas but it seems the fonts are loaded differently or displayed differently from 3.6.0 and 3.7.0. Not sure if I have to adjust what I am doing to make it look good again but, personally, I can't accept how they look. Here is a comparision side by side of the two different versions.
You can see the new hotness on the left and the old and busted on the right. Look at the '2's and 'o's. They are cut-off. The problem seems to show itself on lower font sizes where letters are being cut off. (the 3rd line is using a large font and being scaled down as a temp work around but still doesn't look as good as it should if you ask me...)
Here is a quick program ran in 3.7.0
Same code on 3.6.0
You can see in 3.7.0 that 'J' and '2' is being cut (oddly the 'o' isn't) and gets worse the smaller the font size loaded.
05-17-2023, 01:00 AM (This post was last modified: 05-17-2023, 06:44 PM by mnrvovrfc.)
To enjoy the new font functionality, you have to use _UPRINTSTRING instead of PRINT, and take the time to study what _UFONTHEIGHT and _ULINESPACING do.
As you can see, the new UPrint tends to have extra space between rows, just so letters don't get clipped and overwritten as often. As for the "3" seeming to squash the "2" somewhat, I don't know what the heck is up with that. It's not a monospaced font, so is it designed that way? Or is it a flaw in the new font rendering? I dunno at the moment and something like that will probably take a little looking into to see how it's supposed to look and display for us, and what the glitch might be, if there is one.
Personally, I don't see a real difference between the two commands in the rendering of the font to screen. As a quck example for font size 24, we can see the lower case 'j' is almost half missing from both. I even added a space after j to see if k was clipping it. I have no issues using print or uprintstring, it is similar enough of a case to qprintstring which is/was just as awesome.
Trying the same with Times New Roman. I see no rendering issues. I do wonder if it just happens with the Arial font. Thanks for taking and hopefully it is just an one-off issue with Arial.
WHILE NOT EndOfLife(1)
HappyLife = HappyWife - (Money * Time * Travel * Gifts)
Kids = (NoTime * LackOfLove) MOD NumOfKids
IF Retirement <> Rich THEN YearsOnJob = YearsOnJob + 1 ELSE SeeTheWorld
WEND
Aye. That's why I mentioned them squishing together side by side. Vertically, the new commands give extra spacing to stop clipping, but horizontal might need some tweaking.
Further testing shows that this is a glitch on our c-side of things, and is something that we should be able to sort out and correct in a future patch. For now, you can load your font with the "dontblend" option and it should display without any issues, as showcased below:
Good news is this doesn't seem to be an overtly complex issue to replicate and isolate, and hopefully won't be too hard to fix for when the next version of QB64PE comes out.
(05-17-2023, 02:10 PM)SMcNeill Wrote: Further testing shows that this is a glitch on our c-side of things, and is something that we should be able to sort out and correct in a future patch. For now, you can load your font with the "dontblend" option and it should display without any issues, as showcased below:
Good news is this doesn't seem to be an overtly complex issue to replicate and isolate, and hopefully won't be too hard to fix for when the next version of QB64PE comes out.
Awesome work around. Glad to hear that it won't be a difficult thing to squash. Always looking forward to the next release.
WHILE NOT EndOfLife(1)
HappyLife = HappyWife - (Money * Time * Travel * Gifts)
Kids = (NoTime * LackOfLove) MOD NumOfKids
IF Retirement <> Rich THEN YearsOnJob = YearsOnJob + 1 ELSE SeeTheWorld
WEND