Update

Previous topic - Next topic

matchy

The kerning is cool  :good: :good: and setting the margins in the font editor will probably deal with the spacing.

MrTAToad

With the CLEARSCREEN -1, everything seems to alternate between the backbuffer and the forground buffer, producing a flickering effect.

Code (glbasic) Select
DEBUG RGB(255,255,255)
CLEARSCREEN -1

WHILE TRUE
DRAWRECT RND(200),RND(200),RND(200),RND(200),RGB(RND(255),RND(255),RND(255))
SHOWSCREEN
KEYWAIT
WEND


Try it with the KEYWAIT first and you'll see two completely different screens being built.  Remove the KEYWAIT and watch it flicker :)

MrTAToad

Debug cant be used with the new numeric types :(

This :

Code (glbasic) Select
LOCAL a[] AS double

DIM a[6]

a[0]=1.2
DEBUG a[0]+"\n"


Produces :

"TestTType.gbas"(6) warning : probably unassigned variable : a+"\n"
"TestTType.gbas"(6) error : variable is not explicitly defined : a+"\n"

MrTAToad

Function name checking is a lot tighter, by the looks of things, which is good :)  It spotted a function (in an extended type) that had the name of STRETCHSPRITE...

Kitty Hello

Quote from: MrTAToad on 2010-Oct-29
Debug cant be used with the new numeric types :(

This :

Code (glbasic) Select
LOCAL a[] AS double

DIM a[6]

a[0]=1.2
DEBUG a[0]+"\n"


Produces :

"TestTType.gbas"(6) warning : probably unassigned variable : a+"\n"
"TestTType.gbas"(6) error : variable is not explicitly defined : a+"\n"

it seems the built in operators do not work for these types properly when using them as an argument.

ampos

It seems the "comments inside subs" bug is again in. Thi time no errors, just blank debug window after f5. Anyone can test this?

MrTAToad

Quoteit seems the built in operators do not work for these types properly when using them as an argument.
Thats a pity!

QuoteIt seems the "comments inside subs" bug is again in. Thi time no errors, just blank debug window after f5. Anyone can test this?
Have you got any example code ?