High Definition Picture Viewer CE [ICE]

by **thelastmillennial** » 12 Sep 2019, 02:49

edgar13 wrote:On Cesium the pictures are not read and that display to.

I apologize for the late reply, I'm recovering from a stomach virus. So you are saying that when you run the program straight from the [prgm] menu (and NOT from Cesium) the program detects the pictures and functions just fine. It's only when you run it from Cesium that you are encountering issues? I have absolutely no idea why that would be the case, exactly which calculator do you have? If you launch Cesium then press [mode], what version does it say you have? Have you tried updating Cesium?

If you press [2nd]>[+]>[2]>[Alpha]>[B] do you see all 3 appvars you sent to your calculator? If you sent over the appvars under the included 'Example Images' folder the appvar names should be Pupper.L , Pupper.R , and Pupper.P If you don't see all 3 of them then they wont be detected by the program.

by **edgar13** » 12 Sep 2019, 14:17

I see the three apvars and the program work when i'm not on Cesium v3.2.

by **thelastmillennial** » 12 Sep 2019, 16:49

edgar13 wrote:I see the three apvars and the program work when i'm not on Cesium v3.2.

I'm... completely baffled. I can't reproduce that at all on Cesium 3.2 with either of my TI 84 Plus CEs.

I'll ask MateoConLechuga about this, perhaps he can help me understand what's going on. Until then, just run the program from the [prgm] menu.
If anyone else is having the same issue, please inform me!

EDIT: Unfortunately, Mateo was not able to shed some light on what's going on. The best I can recommend is to try to re-install Cesium, try a RAM reset, or re-install the OS. I'm dumbfounded why your calculator is behaving this way and I'm sorry to say I don't know how to fix it.

by **thelastmillennial** » 16 Sep 2019, 03:26

I've got good news and I've got bad news, the good news is I finally was able to reproduce your issue edgar13! The bad news is, I was able to reproduce your issue, now I really have to figure out what's wrong!

Anyways, I'll get the issue fixed as soon as I can!

EDIT:

I have fixed the issue! Thank you very much for bringing it to my attention! The fixed version is uploaded to Github.