1 hour ago, kliepatsch said:
do you plan to make the UI work with the mouse? Or via keyboard? Or do you just want to provide drawing routines and let the user program handle the interactive part?
My plan was to just provide the drawing routines and let the user handle everything else. I do plan to provide a function that can preserve a window so it can be restored late, effectively allowing for popup windows or message boxes.
48 minutes ago, BruceMcF said:
as would scr2p and p2scr.
The second pair would be particularly helpful to experienced 6502 assembly programmers who are not used to the oddities of both PETSCII and Commodore screencodes
I was thinking of having functions that output strings only accept petscii and then convert it to screen codes. Functions that output/use single character will require screencodes, and then provide a couple of very basic functions for converting to/from screen-/petscii-codes.
I am hoping to be able to keep the size of the generic library within 2K so it can be loaded into "golden" RAM. We will see, it might ned a memory bank for it self in the end.
For now it is just under 400 bytes, but not at all complete yet.