0 Members and 1 Guest are viewing this topic.
Stuff I intend on fixing later:Quote from: MGOS on February 21, 2013, 10:03:09 amI found another bug with Axe compilation. Unlike Axe, zStart doesn't check whether a program is compilable or not, so you can accidentally compile another source file (e. g. a file with subroutines etc.) which is not meant to be compiled as the main program by Axe. It causes Axe to crash or compile another program (like the one directly above or below (?) in the program list). Of course you can avoid this by not doing the On + Sto-> in the wrong place but it happened multiple times when I didn't watch out.
I found another bug with Axe compilation. Unlike Axe, zStart doesn't check whether a program is compilable or not, so you can accidentally compile another source file (e. g. a file with subroutines etc.) which is not meant to be compiled as the main program by Axe. It causes Axe to crash or compile another program (like the one directly above or below (?) in the program list). Of course you can avoid this by not doing the On + Sto-> in the wrong place but it happened multiple times when I didn't watch out.
Kind of update: fixed the issue with it freezing on inputs fixed crashing when trying to install on the wrong OS fixed (probably) the C000 issue a few people had on 83+BE's fixed an issue involving interrupts and port (07)Stuff I intend on fixing later:Quote from: MGOS on January 24, 2013, 10:01:54 amI came across this "bug" multiple times now:When you turn off the calculator while you're editing an archived program (the copy of one), and zStart wants to store the edited version and GarbageCollect appears, the LCD turns off and and it doesn't react on any key presses (calc behaves like turned off, but it isn't) before you can do a GarbageCollect. You need to remove the batteries and lose the current progress which is kinda annoying :/Is there someway you can prevent the calc (or its peripherals) from turning off when the program isn't saved yet?Quote from: Freyaday on January 24, 2013, 03:26:24 pmCan we have find|replace?Quote from: MGOS on February 21, 2013, 10:03:09 amI found another bug with Axe compilation. Unlike Axe, zStart doesn't check whether a program is compilable or not, so you can accidentally compile another source file (e. g. a file with subroutines etc.) which is not meant to be compiled as the main program by Axe. It causes Axe to crash or compile another program (like the one directly above or below (?) in the program list). Of course you can avoid this by not doing the On + Sto-> in the wrong place but it happened multiple times when I didn't watch out.If after a few days, there are no glaring mistakes in this, I'll upload it to ticalc.org finally.
I came across this "bug" multiple times now:When you turn off the calculator while you're editing an archived program (the copy of one), and zStart wants to store the edited version and GarbageCollect appears, the LCD turns off and and it doesn't react on any key presses (calc behaves like turned off, but it isn't) before you can do a GarbageCollect. You need to remove the batteries and lose the current progress which is kinda annoying :/Is there someway you can prevent the calc (or its peripherals) from turning off when the program isn't saved yet?
Can we have find|replace?
Nice!I'll download it in a bit more than a month, I already sent some stuff (including my z80 calc) back to germany......
Just caught up on the last 9 pages and updated, looking good Tho it might be worth changing the text in-app for the version number
So are there plans to integrate/do something similar to xeda's MenuKey? On+# doesn't do anything in the program editor anyways.
Where is the update?
I've found that some of the ion routines don't quite work as i thought, for example ionPutSprite doesn't seem to be drawing to the gbuf. I think it's because you have ld de,$FE79 (TilEm2 calls it symTable+19) instead of ld de,($FE79) in the putSprite routine. I haven't tested out the 83+ version yet, but i'll do that soon Thanks for the update!
Not sure if this has been asked for before, but would it be possible to bring omnicalc's line-clearing behavior to the program editor?What it does is if you go to the middle of a line and press clear, it only clears after the cursor.