Alright, a couple of ideas:
1. Using Rcl from Archive.  I'd love to be able to recall archived programs into the current program.
2. Another mode for Fast Memory Timings: Make it so it works outside of when programs/Apps are running, but not while they are running.  This, if I'm correct, could make archiving source and editing faster while still having the compiled program run at its correct speed (Axe example).

Alright, a couple of ideas:
1. Using Rcl from Archive.  I'd love to be able to recall archived programs into the current program.

Done

2. Another mode for Fast Memory Timings: Make it so it works outside of when programs/Apps are running, but not while they are running.  This, if I'm correct, could make archiving source and editing faster while still having the compiled program run at its correct speed (Axe example).

We've already talked, 14% faster isn't enough to make a big difference.

I love the label menu, but Axe now supports labels of up to 5 characters

Maybe later, but that would require quite a bit of rewriting.

and they can include lowercase letters. I would love to see zStart support this.

Done

Also, would it be possible to have shortcut keys to jump to the top and bottom of a program? I know DT made a program that does this, but having that hook included in zStart would be awesome.

Done


These will definitely be the final features added to 1.3 because I ran out of room today. Spasm gave me this message: "exporter: warning SE802: Only 48 bytes are used on the last APP page." Which meant I had to go back through my code and optimize out 48 bytes, which wasn't really that difficult. But, optimizing out enough bytes to add in more features is pretty much a no.

So, I'm going to leave 1.2.13 here for you guys. I'll be gone for a week. When I get back, if I see there are no glitches, it's off to ticalc.org with it. (I'll probably still be able to do a few things while I'm gone though, so don't worry.)

And don't forget, 1.3 will be the last version that is 1 page. All versions after that will be 2 pages. So if space is an issue, you better speak up.

coolio! i love that you just keep adding things to this

Lemme start by saying, I love the new features.

That said, I'm having some rather grievous issues with the run on RAM clear function.

I'm not sure if the culprit is Axe 1.0.2 or zStart 1.2.013, as when zStart was the only thing installed on my calc after a ROM clear and fresh OS installation, the run on RAM clear feature worked perfectly. I then proceeded to send my other apps back, though Axe was the only one I installed. I wrote a simple program, just drew a few rectangles, inverted some text, and XOR'd a sprite, compiled and ran it. No issues. Then, when I RAM cleared, zStart did not kick in, and I've had some interesting issues when I tried to uninstall and reinstall the run on RAM clear feature, such as a ERR: MEMORY when I went to the memory clear menu, or my contrast value being 104. If run on RAM clear is not installed, I have no issues.

I've also posted in the Axe Bug Reports topic, as I was unsure of what caused this problem.

Didn't work... I deleted the appvar and redid everything.
I tried a Arc Vars clear, and compiled and ran a program in Axe. It seems to be working...

Until I messed with the Axe Settings in zStart that is! I had left the Axe hook turned off in zStart, but I still set up a compile shortcut, and compiling and running worked fine. As soon as I turned the hook on in zStart, and compiled a program using a shortcut, the run on RAM clear function stopped working! I turned the hook off again, and run on RAM clear works!

I think I've isloated the issue, but I'm still unsure of whether it's Axe or zStart's fault.

Is it possible to make an option that the clock won't get reset on a ram clear?

Zstart seems to be quite a nice piece of code =]

Btw, dunno if it's related to the os version, but my clock is never affected by resets, at least ones voluntary triggered by me (defaults/ram/all).
I use our good old 2.43.

I'm using 2.43, and it resets for me (tho that's on error crashes, not mem menu resets).  I'm not sure if the OS matters much in this case, anyway..?
Pretty much the only time I set the clock is to use MSD8X, so all my backups aren't from 1/1/01

Also, regarding the clock saving...

Quote from: thepenguin77 on May 16, 2011, 08:22:49 pm

Quote from: alberthrocks on May 16, 2011, 07:47:57 pm

2) Clock saving. I know this isn't technically "possible", but that's if you are looking to save every second of the clock in an ASM program (Or any program) I'm just asking to save the clock when you execute a program or leave a program. Applies to apps too, if possible. It would save me some time (hehe, get it? ) to set the time. And of course, a manual shortcut as needed

If I did clock saving like that, it would be off by about 1 minute per ram clear. Which would compound every time. And what is worse is that for every second you wait without pressing the ON button, the time gets 1 more second off.

Thank you, I've answered that question so many times I wasn't going to respond

OS 2.43 is the first OS to not reset the clock on manual resets, the previous ones did. However, hard resets do reset the clock. In fact, I believe that was all that was changed for 2.43.

Just had a random thought: is program writeback enabled?  I'm guessing there isn't enough room for an option, tho

The programs always write back if they are changed. I run a 16 bit checksum on them, and if the checksums before and after don't match, I write the program back. In ram, the program gets written back every time, but that's entirely different. Also, I didn't add an option because I feel like you would always want the program to write back if it was changed.