jEmplode 34 - Autoupdating jEmplode + Updates UI

This is a relatively small release, but I just wanted to get this out there so it can be used for a 35 release in a couple days... Basically, you've got autoupdating jEmplode in there (turn it on in the Tools.. Options) and a UI on updates (Hijack and jEmplode) that shows the ChangeLog for the version and lets you optionally upgrade or not.

34 added VersionTracker UI that shows changes before updating
34 JEmplodeVersionTracker
34 added jEmplode auto update options to Tools...Options

Cool features! Haven't seen them work yet, because I'm up to date on both of them.

One note. There is but one menu item which requests manual updates, and it seems to try to update both Jemplode and Hijack (good), but the name of the menu item is still "Update Hijack" (bad).

Oops .. you're right.

Yeah that rocks !!!


I 'll have one request for the update (JEmplode and Hijack).

Could we have a folder to fill in the options , this folders to save the kernels and Jemplode Archives.

Actually, I am doing that, cos I want to keep all kernels versions and Jemplode also.

That would be nice ....

Yep .. Can do ...

Wow Thanks !!!!

Mike,

I'm trying to figure out how Tony's player sometimes skips the (custom) animation on start-up. The one thing I can think of is "alignment" in memory.

Is it at all possible in any way for JEmplode to use non-4byte alignment for either the start of the offset table, and/or for any entries within the offset table?

Hijack v253 now disallows animations whose offset table is not 4byte aligned, but it doesn't bother looking at the table entries themselves.

Thanks

-ml

If it does, it's a bug ... I can't really think of how it would happen.... Do you have a particular animation that consistently fails, or just randomly?

I've asked Tony to see if he can send me his flash image.. he has had animations fail to play a few times now (still rare, though), and I've looking at everything to try and figure how the heck that could possibly happen.

Thanks

-ml

I'll take a more thorough look at the code tonight too ...

I just looked through a flash dump tfabris sent me, and all of the offsets look just peachy fine. So that's not it.

Cheers