A set of simple Reportlab demostration files for a Python User Group presentation.
While in edit mode, cursor keys inside a string produce PETSCII control characters as expected from the recent commit. However, outside of a string they do nothing (i.e. the cursor doesn't move).
The cursor keys still work while not in edit mode.
One solution could be to expose the Kernal trig routines and possibly provide helper words to precompute tables of a given length if needed.
e.g. sintbl ( length -- addr )
Working great now! Thanks.
https://user-images.githubusercontent.com/1018548/208598600-42362afe-67f9-4141-80ba-53d586aa9a15.mp4
This error seems to prevent the .crt and .d64 files from being produced, but I can at least test the v editor from this screen while the "make" build is stalled. The control characters are working fine in this build. :-)
When I run the build I get the attached message in Vice.
I'll give it a try, thanks.
From a user's perspective, a special "string insert mode" would be ideal.
The screen editor in immediate mode can take advantage of PETSCII control characters in strings, e.g. left cursor, home, reverse on/off.
The vi editor doesn't seem to allow entering control characters. Is this a feature you could add?
Hi @machour. Name change done.
Update contributors.xml with userName IanWitham