0 Members and 1 Guest are viewing this topic.
How far are you with the update? TI 84+ SE won't install the ram clear hoook, although it says success.
When MathPrint is enabled, any of the shortcut key actions used from a menu eject control back to the home screen.
Here's a big (code size-wise) one that probably isn't super important, but would be neat if it existed: instead of having individual options to control a few defaults, include an option that saves basically all settings as defaults (everything currently available and everything in MODE). If you were crazy enough to add this, you might also be crazy enough to be interested in adding a second option that does the same for the WINDOW and FORMAT settings.
Feature request: when editing archived programs, they don't get rewritten back to archive if nothing is changed.
Shortcut key actions do not work in contexts other than the home screen. This includes menus launched from these contexts.
When uninstalling the run on RAM clear functionality finishes, "No" is printed over "Yes". But no erasing is done, so you end up with "Nos". A simple fix for this would be to append a 3-wide space (character code $EE (could a small font hook with a wider "s" ruin this fix?)) to the end of the "No" string.
The "Select font" option sometimes says "No" when no font is selected, but other times is just blank. I suspect that one of these behaviors is a bug. If showing the string "No" was the intended behavior, may I suggest a slightly more fitting string, like "None"?
A common, minor oversight of many programs/apps: if you use plotSScreen, you should mark it as dirty with set graphDraw,(iy+graphFlags).
A negative feature: remove the confirmation on setting shortcuts? I don't think I've ever accidentally hit any of those shortcuts, so the confirmation seems a bit unnecessary to me. If you do want to keep them in, though, it wouldn't bother me much. But if you do, can you display some text between "Confirm" and "Set" (perhaps "Working..." or "Setting...")? On my calculator, the option setting/saving process takes about 4 seconds. It may take a non-trivial amount of time on others' calculators as well, and during this time, the calculator appears frozen.
A shortcut to toggle MathPrint.
All my stuff has been addressed! Awesome! The MathPrint toggle should actually be pretty useful if I'm ever doing serious math on my calculator. I played with it for a bit and noticed a few things:Changing from Classic mode to MathPrint mode leaves the entry history intact, but changing in the other direction does not. Why is this? The entry history seems to stay intact when changing modes the old-fasioned way from the mode screen.Changing from Classic mode to MathPrint mode sometimes doesn't return the cursor to the top left corner of the screen, and sometimes that happens as well as text being left over from Classic mode. The first case is definitely a bug, and the second case is probably two bugs in one, although it's actually pretty cool when the second bug happens. It seems like switching modes almost invisibly.Regarding the shortcut to enable MathPrint not working unless it has already been enabled once: perhaps the above bug is somehow related to it? If not or you otherwise can't easily see how to fix it, can you do something sneaky to always let MathPrint load up on RAM clears, but after it has been enabled, immediately switch to Classic mode if that default is set?Also, another thought popped into my mind. You know how a while ago I mentioned that Omnicalc's quick apps menu doesn't register a context change until after any executed app returns to the OS? That may be a hard Omnicalc issue to fix, but I realized there are other issues with Omnicalc that might be (perhaps more easily) fixable. For instance, enforcing that parentheses assistant, the entries menu, and RAM recovery are disabled when MathPrint mode is enabled, and returning them to their original settings when Classic mode is enabled. It also may or may not be feasible to kill the partial line clear functionality when MathPrint mode is enabled. (I got the impression that you try to keep your key hook fast by only having ON+___ shortcuts so you can abort if ON is not pressed, but this check would need to occur before that)
You managed to ask this really well actually. You made me feel bad because my app wasn't working right, and you managed to ask on a friday when I actually have some free time.
Thanks a lot for your interest in assembly for TI calculators and the community Jacob/penguin!
Also I'm looking forward to your news Hayleia.
Quote from: Pawnerd on September 22, 2013, 11:37:39 amThanks a lot for your interest in assembly for TI calculators and the community Jacob/penguin!Erm, his name is not Jacob at all.Also, I'll use that post to host screenshots of zStart so I can make a decent post on TI Planet about this app (I'll do this tomorrow maybe).
If you are going to do something front page with it, let me know so that I can upload a full .zip of it. The one I uploaded is missing a few things for being a full release.
Quote from: thepenguin77 on September 22, 2013, 03:48:05 pmIf you are going to do something front page with it, let me know so that I can upload a full .zip of it. The one I uploaded is missing a few things for being a full release.Apparently, no one is against my article going to front page (I just have to finish it with those said screenshots). And even if it doesn't go to front page, a full zip is still a good idea, isn't it ? ^^
Author
Topic: zStart - an app that runs on ram clears (Read 333196 times)
