Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Possible bug: Word-wrap oddity
#11
Aye, you'd have to determine the size of your words via _PRINTWIDTH to know where to word wrap them, but the glitch I'm talking about is easy to see:

LOCATE y, 800 in your demo.  The screen is from 0 to 799.... 800 should toss an error as it's off-screen, but it doesn't.

LOCATE y, 0 should print at the absolute far left of a line, but it doesn't.  It tosses an error.

LOCATE and non-monospaced fonts are indexed base 1 instead of base 0, which they need to be to do things correctly.  I'll dig into it more over the next few days and see if I can't sort the issue out for us.  (And then I'll try and sort it out for PRINT in general, to boot after that.)  ;D
Reply
#12
@admin and @hanness



Something that might be of interest for printing max to the screen size: https://qb64phoenix.com/forum/showthread...72#pid1672




Pete
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Is this a bug with Round or is it just me BarrySWTP 10 1,244 07-07-2025, 08:40 PM
Last Post: BarrySWTP
  Exiting FOR NEXT, maybe a bug? Version 4.1.0 on Linux Circlotron 4 843 05-09-2025, 02:22 AM
Last Post: Circlotron
  I have fallen in a bug or weird behaviour TempodiBasic 2 671 10-08-2024, 06:09 PM
Last Post: TempodiBasic
  3.13.1 bug report - keyboard characters swapped Circlotron 3 999 06-03-2024, 05:16 AM
Last Post: Circlotron
  I need input on a possible bug in v3.5.0 TerryRitchie 50 8,411 05-22-2024, 07:03 PM
Last Post: TerryRitchie

Forum Jump:


Users browsing this thread: 1 Guest(s)