INPUT BUG: Workaround with SHIFT+SPACE and Controlcodes for Cursor movement doesn't work about basicv2 HOT 5 CLOSED

You should be able to use placeholders for those in the text file. Either by using

{shift-space} {left} and {up}

or by using the codes directly like so:

{160} {157} {145}

from basicv2.

Regarding the other two parts of the issue:

Console support: Should be able to handle SHIFT+SPACE now

BasicShell: Control codes can't work in this one, because it's a Java text area in disguise and not a proper C64 console at all.

from basicv2.

Test console with the program:
the trick is not working: when there is no inut (return without any inut is pressed), then a PET or C64 reads a SHIFT+SPACE from screen. But with console support it seems that A$ is empty in this case and there is a illegal quantity error in line 20.

Regarding BasicShell:
I must admit that I don't know the text area component, but I believe you that the handling different code tables is terrible. Is changing the position in this component really so difficult ...

from basicv2.

The SHIFT-SPACE hack can't work in the console, because it's just an output device. Input is read from the keyboard, not like on the C64 from the screen. So "preloading" the input value won't work.

About the text area: It's meant to be used as a compontent for the user to type/edit some text. Just like a text area on a HTML page. The fact that the shell uses it for both, input and output is already stretching it beyond what it's supposed to do. You can set the cursor programmatically, it just doesn't work in the way it's supposed to to emulate control codes. That's why CLEAR/HOME works, but HOME doesn't, for example.

from basicv2.

Frankly spoken I was surpised that the message came so fast, that the problem with SHIFT+SPACE is fixed. I assumed more effort and my assumption was correct.

The SHIFT+SPACE has minor priority, but the cursor movement would be nice.
Perhaps you will have a good idea after you made your last integer optimization ;-)

from basicv2.