Qbasicnews.com

Full Version: KILL bug
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2

Anonymous

the KILL command does not work when in a screen mode set in gfxlib



Code:
kill "thing.txt"

works


Code:
screen 13
kill "thing.txt"

doesnt[/code]
Worked fine in 0.13:

Code:
kill "thing1.txt"

screen 13
kill "thing2.txt"

The gfx lib doesn't hook KILL or something like that.

Anonymous

thanks, it was my fault, i didnt close the file before trying to KILL it...


btw, what do you mean "hook" it ?
The gfx lib, when SCREEN is called, hooks many routines like PRINT/INKEY$ to take control of them, that are by default controlled by console module.

Anonymous

oh ok

thanks :D
Quote:thanks, it was my fault, i didnt close the file before trying to KILL it...


btw, what do you mean "hook" it ?

He means that once you try FB, you're hooked.... :rotfl:

Anonymous

Quote:
Cha0s Wrote:thanks, it was my fault, i didnt close the file before trying to KILL it...


btw, what do you mean "hook" it ?

He means that once you try FB, you're hooked.... :rotfl:

haha word.
um i noticed an inconsistency with gfxlib too, that the screen function reads chars off the console even when you're in a gfx mode. like
Code:
print "a"
screen 19
print "b"
print chr$(screen(1,1))
sleep
="a"
Why not get rid of the console, then?
if you mean compile with "-s gui" it doesn't matter, same output
Pages: 1 2