07-16-2023, 11:00 PM
(07-12-2023, 06:03 AM)PhilOfPerth Wrote: While experimenting with Chr$(), I find that Chr$(95) (the underscore) is the only one that is not displayed in a 16-bit screen mode. (it displays in 32 - bit mode)This should actually be fixed, if you use the new UPrintString functions. The issue here is a glitch in the print routines with certain fonts basically suffering from clipping/truncating in the old versions of QB64 with PRINT.
I suspect this is because the character uses the lowest row of the cell (row 8). Is this the reason?
But Chr$ 92, 93, 103, 106, 112, 113, and 121 (mostly serif characters) all appear to use row 8, and they display in full.
Kindly share what version of QB64 you were testing on which had the underscore disappear on you, (and then give it a shot in the latest release and see if the issue still persists), along with the font name and size, and we'll test it and see if it's something we can fix, if it's a bug in QB64's side of thing. Properly rendering fonts is a little more complex than most folks think it is, and clipping due to rounding issues and other such things isn't all that uncommon. Sometimes, it takes a little persistence and a lot of debugging grease, before everything works 100% as expected. (If it ever does.)