Re: HP 42S Text Editor Message #10 Posted by Christof on 17 Apr 2003, 2:39 p.m., in response to message #6 by Christof
No matter what, this is going to be a bit hackish sinc eI can't extend the 42S any. (right now, anyway)
I've been using registers 40 through 49 for the program itself, I'm wondering if I shouldn't make part of the code require a SIZE 120 or something and use more indirection?
Will people be using a lot of code that will conflict with my registers?
(for memory pointers, just the memo functions will take up somewhere around 600bytes. the full text editing system including file concatenation, a faked directory structure, and such may take as much as 2k- though probably less.)
Two other thoughts I've had involve structuring the memory.
I can use individual matrices per 'text file' and a master matrix to keep a 'directory'
or I can reinvent LIF on the 42S and make one large matrix with an internal directory structure to find the text files, all of which will be included in it. This takes longer but will look cleaner when doing things outside of the text editor.
- one of the reasons this is taking so long is I keep playing with differnet methods like this.
I've also given up on the GETKEY based input system. many people hate the 32Sii alpha keyboard anyway, and I don't have any reasonable system for holding keyboard templates down on a 42S.
I may try that method again later, but it will eat memory and cpu cycles like candy... (no problem for me at 32K ram, but not everyone has that)
|