Possible bug: Word-wrap oddity

[Pete]

@hannes

It is fun, and, at least for me, it was a big reason for sticking with a true BASIC language. The names of the statements make sense, are easily remembered, and many of the accompanying statements start with the root word.

@admin

There's another thing that I lost in memory, width 10, not 8. When you mentioned that, I vaguely recalled a project from three or fur years ago where I worked with the lucon width size. THANKS! You know the saying, "I've probably forgotten more information in life than most people ever had." is really not comforting.

Anyway, i = 1 to 80 prints 80 asterisks at width 10 pixels, makes perfect sense, but like I showed hannes, the monospace element does need to be present to do that or, apparently, the system doesn't consider the font width to be fixed at 10 pixels, as _FONTWIDTH without monospace added would be zero, (undefined), instead of 10.

So here is a little demo of not using and using monospace in the font declaration to illustrate this...

Code: (Select All)

handle& = _NEWIMAGE(800, 600, 256)
SCREEN handle&

fontpath$ = ENVIRON$("SYSTEMROOT") + "\fonts\lucon.ttf" 'Find Windows Folder Path.
font& = _LOADFONT(fontpath$, 16)
_FONT font&
_DELAY .1

PRINT "Demo without monospace added.": PRINT
FOR i = 1 TO 80
    ' With monospace added, this will print as one line.
    PRINT "*";
NEXT

fontpath$ = ENVIRON$("SYSTEMROOT") + "\fonts\lucon.ttf" 'Find Windows Folder Path.
font& = _LOADFONT(fontpath$, 16, "monospace")
_FONT font&

SLEEP

CLS
PRINT "Demo with monospace added.": PRINT
FOR i = 1 TO 80
    ' With monospace added, this will print as one line.
    PRINT "*";
NEXT

Pete


I may be old, but I'm not.. ah I'm not...