GFA BASIC TOSWIN2 and INPUT

[peterlane]

I downloaded GFA BASIC for the Firebee today (from http://gfa.atari-users.net/atari/html/gbe.htm), and have been experimenting with some simple programs.

I am using MINT (and XaAES).

Output (using PRINT) is working fine. I can compile a .APP program, and run it using TOSWIN2 to see the output.

However, as soon as I use INPUT, things go a bit funny.

e.g. this program

Code: Select all

LINE INPUT "What is your name? ",a$
PRINT "hello ",a$


When I run this in TOSWIN2, as I start to type, the cursor moves up a line on screen with each character I type in.

Is there a way to get input to work correctly under Mint (with or without TOSWIN2)? I would like to experiment with some simple text I/O programs using GFA BASIC.

I spent some time searching, but didn't find any solution. (There's a mention of a Bconin() problem in http://gfa.atari-users.net/stg/gfabasic.htm when using INP: is that the problem here?)

[lp]

GFA's input commands assume a single-tasking environment, as in the whole screen. If you close TOSWIN2's console window you will notice they work as expected, but then dirty up the desktop. I don't know if this is some oddness of TOSWIN2 or what, it's never worked for me either. If you are using the GBE library, you can do this instead:

Code: Select all

OPENW 1
CLEARW 1
LINE INPUT "What is your name? ",a$
PRINT "hello ",a$
~INP(2) !wait for a key press
CLOSEW 1


GFA will redirect PRINT and INPUT into it's own built in windows. These built in window commands are very simplistic, they will not auto buffer the contents, nor redraw if overwritten. They can be used in a GEM environment for tinkering around, to avoid messing up the desktop though. I recommend never using them for a finished application.

[Playmobil]

Hello Lonney... Sorry for my english...

Why use LINE INPUT ?

And not just INPUT or INPUT #1 ?

[peterlane]

GFA's input commands assume a single-tasking environment, as in the whole screen. If you close TOSWIN2's console window you will notice they work as expected, but then dirty up the desktop. I don't know if this is some oddness of TOSWIN2 or what, it's never worked for me either.

Thank you. Your suggested work around does the job.

Why use LINE INPUT ?

I can see just INPUT should be enough, though the manual says LINE INPUT has the difference that it will also accept a comma in the input string.