Well, I hope that Unsigned still works at least.

Good luck stopping unsigned lol. I made that program possibly the most annoying program for TI to debug. Not only is the entire program encrypted, but it has like 8 different hardware checks that it performs to make sure it's not running on an emulator. My favorite part is that a few of the checks crash it, a few of the checks freeze, and finally, the last few checks make it look like it worked when in reality nothing happened.

Basically, TI is going to have to write some code in order to figure out how that program works.

I don't really have the time right now to think about how you would actually go about this, but I would think that trying to represent the cube state compactly would be a big mistake.

The key issue with a program like this is going to be speed. You might run into memory problems, but, I think more realistically speed is the primary issue.

With that in mind, I think you should try to figure out how you are going to actually solve the cube, and then pick the data structure that allows you to run the simulation the fastest. It would be a little silly if 75% of your calculation time was spent compressing and decompressing the cube states Besides, there are only actually 22 blocks that you can move. Representing each one as a byte would only be 22 bytes per cube.

oh. Duh.

now all we need is an 8 level greyscale movie player...

Wasn't there something like that made before? Some 8xk of The Matrix?

An 8 level grayscale viewer would be a little silly. Each frame of the video only gets around 4 LCD refresh cycles. When you consider the fact that 8 level grayscale needs a 7 frame loop to achieve 8 colors, you see why this would be a little pointless.

However, maybe you could write a video encoder to take advantage of this and purposely alternate the color of a specific pixel so that it approximates 8 colors. This seems doable, but maybe a little mentally taxing

Also, if you don't want sound, use fourvid. It's uses .png compression and gets around 50% compression.

Quote from: thepenguin77 on September 22, 2013, 03:48:05 pm

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.

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 ? ^^

Ok, I fixed it. I usually don't upload the full one because inevitably I always say "I'm going to upload this to ticalc.org next week if there are no errors". And then there are errors and then I never upload it to ticalc.

Edit:
   You might also want to mention that zStart and MathPrint don't get along nicely if people have trouble with stuff.

Ok, I figured out all of the issues.

1. zStart and Mathprint don't get along at all. This is something I need to fix eventually, but that's why the program editor crashed and why you couldn't properly set the program to run on ram clear. The simple fix is just to change it to classic in the zStart defaults menu
2. The program that you want to run on ram clears has to be archived (otherwise it's just going to get deleted) You can press ON + * in the program menu or in the editor

3. It did install on ram clear. You just didn't tell it do do anything (The best way to check is to enable the "old ram clear", that will change the ram clear screen).
4. The lowercase is a function of the calculator that zStart turns on, at one point I meant to make it an option, but I forgot and it's on by default now.

How far are you with the update? TI 84+ SE won't install the ram clear hoook, although it says success.

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.

I fixed the running on ram clear issue. It was a stupid mistake by me, but the bad news is that it corrupted the OS. On 2.55 it made it so that the calculator will crash if you pull the batteries out from the homescreen (it usually doesn't). On 2.43 and 2.53 the calculator will go into a boot loop if it crashes. And on 1.19, all the menus glitch out. So if you tried to install the faulty version, you should probably resend your OS. (sorry)


First I'm just going to list these ones that I didn't do yet but want to do:

When MathPrint is enabled, any of the shortcut key actions used from a menu eject control back to the home screen.

This is actually coded like this on purpose, but I should find the proper way to do it.

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.

Maybe...

Feature request: when editing archived programs, they don't get rewritten back to archive if nothing is changed.

This isn't as easy to add as I thought, but I should add it.

Shortcut key actions do not work in contexts other than the home screen. This includes menus launched from these contexts.

Someday, but I have to handle every menu differently because a lot of the hooks require closing the edit buffer.


Things I did do:

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.

I fixed it in a less pretty way. I can't modify no because I right align it sometimes.

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"?

Again, I can't change it to "None", but it will at least say "No".

A common, minor oversight of many programs/apps: if you use plotSScreen, you should mark it as dirty with set graphDraw,(iy+graphFlags).

I added this to the main app, the two help programs, and the label finder.

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.

Run indicator + fast mode fixed that pretty well

A shortcut to toggle MathPrint.

Of all the things I added, this was by far the hardest. It's really hard to change this from a key hook.


So update!!

• Added - ON + MATH - toggle MathPrint
• Fixed - run on ram clear (it finally works)
• Fixed - a few graphical issues within the app
• Fixed - Setting shortcuts is a little faster

I have the full .zip attached this time. The two zHelps got updated if you actually use them.


Edit:
   So, you have to have MathPrint open at least once before you can use my shortcut. I'm working on why.

Edit 2:
   Changed to a full release .zip

Ok sweet, all of that worked. Thanks! But one thing, i'm able to open programs and read them, but how would I modify them? (and save them, of course)

Now you're treading into deep waters. There are two ways you can modify and them neither are easy.

1. Modify them in a patch way
This method is going to involve hex editing. In the simplest case you can simply patch the files without changing their size. To do this, I'm going to recommend calcsys. What you need to to is look at the original file (in ida) and find the code you want to change. Then, you need to determine what you want to change it to. (I'd recommend just making a fake little program with your code, assembling it, and then looking at what it assembled into). To actually change the file, make sure it's in ram, then open calcsys>6>1>1>find it. Now, take note of the "data loc". To find the location in this program that you want to modify, take (real address) - 0x9d95 + (data loc) + 4. Then press Alpha + H > Alpha + G > type location. From here you modify the necessary bytes and hope it works.

If you have to change the file size, well, I'm not going to write how to do that because it's really annoying.

2. Completely reassemble the program
This method is a lot more work, but you have way more flexibility. You need to completely disassemble the program in IDA. This means that you have all the code and data sections mapped out and all pointers actually pointing to labels (the most important part). If you manage to get this far, you can tell ida to produce a .asm file which you can then edit just like any other program. I have successfully used this method to rewrite a game, but, it is a bit of work up front.


Btw, you're getting these really long replies because you keep asking questions about what I love doing with the calculator.

There are three ways I see to go about this: the two easier ones are either the menu hook or the raw key hook.

The menu hook gets called rather frequently when the menu shows up so you might be able to tweak some stuff (set a breakpoint at the start of your hook (after checking for the correct menu) and look around at what has been set up. This is your best bet for tweaking stuff). The raw key hook would basically be you completely changing the function of the program button. I don't know what your plans are, but this is probably the more difficult of the two because you'd have to make your own menu.

If this is the first time you've used hooks, you should check out my hook guide.


Now, the third option is patching the OS. This is pretty tricky actually and probably isn't the option you want to use. But, of course, we don't know what you want to change.

Finally, you've sadly picked the worst menu to change. The program menu is generated dynamically and is a pain to mess around with.