Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
printing characters > chr$(127)
#14
255 for QB64PE, for whatever reason, just maps directly back to 32.  (It's just another plain, normal blank space.)

In the code I posted, I had it map to those unicode values, so you actually have two entries for a blank space.  The only way you'll have anything different is if you:

 _MAPUNICODE 255 TO (a different value than 32)

Why Galleon decided to set it up in such a manner, I don't know.  If I had to guess, it'd be so users could reserve that one character as a quick-toggle to swap it in and out for whatever character they might need to display otherwise.  By default, it's just a space -- but we already have a space (32), so it can be replaced and customized on the fly as needed.
Reply


Messages In This Thread
printing characters > chr$(127) - by madscijr - 03-08-2025, 05:19 AM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 06:48 AM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 06:54 AM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 10:05 AM
RE: printing characters > chr$(127) - by madscijr - 03-08-2025, 03:07 PM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 03:35 PM
RE: printing characters > chr$(127) - by madscijr - 03-08-2025, 03:43 PM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 04:25 PM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 05:30 PM
RE: printing characters > chr$(127) - by madscijr - 03-08-2025, 09:20 PM
RE: printing characters > chr$(127) - by SMcNeill - 03-08-2025, 11:06 PM
RE: printing characters > chr$(127) - by madscijr - 03-09-2025, 12:01 AM
RE: printing characters > chr$(127) - by madscijr - 03-09-2025, 02:32 AM
RE: printing characters > chr$(127) - by SMcNeill - 03-09-2025, 03:17 AM
RE: printing characters > chr$(127) - by madscijr - 03-09-2025, 10:56 PM
RE: printing characters > chr$(127) - by madscijr - 03-09-2025, 11:46 AM



Users browsing this thread: 13 Guest(s)