|
|
| Line 1: |
Line 1: |
| − | About 99.9% of the BASIC programmers have used this: the program editor, where you can edit your BASIC programs. It's pretty easy to use - for people who don't know assembly. If you want to learn how the program editor works, please continue reading, and otherwise, just get out away ;)
| |
| | | | |
| − | Of course, it's much more complex, than just "opening it, edit the BASIC program, and quit it". I want to discuss 3 steps:
| |
| − | * Set up
| |
| − | * Editing
| |
| − | * Closing
| |
| − |
| |
| − | The second point is the hardest, so let's start now!
| |
| − |
| |
| − | == General information ==
| |
| − | When you (want to) open the program editor (or buffer), you see the cursor flashing. That is very important to know. When you open the editor, the OS places ALL the remaining RAM in it. This is very useful, because if it don't, each time you add a token, it need to shift the whole RAM 1 byte. This is very time-consuming and annoying. Instead of calling each time _InsertMem or _DeleteMem, it has to move the other programs in RAM twice, before and after editing. At the CE, you have almost always 65000 free bytes in the editor, enough to make awesome programs. Very nice and handy, but not in 1 points. It means you can't allocate other memory. This means no creating or resizing other programs, and no pushing to or popping from the floating point stack.
| |
| − |
| |
| − | You have 2 possibilites: or create it yourself entirely, with key checking, and displaying menus.... but that's hard. Let's see if there are other ways to do this! I assume you have enough acknowledge of ASM to understand this.
| |
| − |
| |
| − | == Set up ==
| |
| − | Be sure to have the program name in OP1.
| |
