Are you sure Pic2 actually exists ? It must since you use GetCalc() without a size word.

I have no idea what that would be happening... If the source file is archived, I would first suggest unarchiving and rearchiving it; Axe occasionally has issues with archived source files, but this usually fixes it. If compiling it still results in the same error, can you post the full source code (in its original 8xp form in case there's some weird token data issues)? And/or if you're using Axe 1.2.1 (which I hope you are!), can you press STAT when the error occurs and relay that hexadecimal error dump info?

You are correct; the bug does indeed exist, and it's because I made a stupid! It appears that I optimized string data parsing a little too aggressively in 1.2.0, but I've fixed it now and the fix will be in the next release of Axe. If you would like a workaround in the meantime, you can replace "Pic2" with [07600100].

Well, I use an application named CalcUtil, and I found two bugs ; one is that, because I'm able to edit archived programs (using CalcUtil), I often compile archived programs, and I (also) get often an ERROR:UNKNOWN, and my calc freezes.
The other bug is that when I get an error, I unarchive the program to find the error (using the [prgm] button), but if I edit the program, the calc freezes and I lose the data... I know this is related to my using of CalcUtil, but if you could fix this, it would be great !

To edit archived programs, I would highly suggest using thepenguin77's zStart instead of CalcUtil. CalcUtil's archived program editing function is known to be buggy, but zStart's is fairly solid. In addition to editing/running archived programs, you get a load of other amazing features. There are too many to list them all, but I'll list some of my favorites for code developers.

Some awesome general program editing features include automatic re-enabling of hooks and lowercase mode on RAM clears, copying and pasting lines of code, accidental line clear restoration, and navigating programs by instantly jumping to any label. There are awesome Axe-specific features too, including the ability to go to errors in archived programs just like unarchived programs from the compile error screen, and a really cool feature, the ability to compile an Axe program, test run it, and return right back to the same spot in the code editor you started at when your program exits, all with just one key combination!

Anyways, that's probably enough plugging for zStart. Regarding the unknown error, I'm fairly confident I know what causes that and a fix for it is in the pipeline.

Quote from: Runer112 on August 02, 2013, 02:32:52 pm

To edit archived programs, I would highly suggest using thepenguin77's zStart instead of CalcUtil.

Ok thanks for the suggestion I'll try when my calc will work

Quote from: Runer112 on August 02, 2013, 02:32:52 pm

Regarding the unknown error, I'm fairly confident I know what causes that and a fix for it is in the pipeline.

Ok, then I'll check for updates every day (or more)

I'm not sure the next version of Axe will be coming out that soon. there are still things I want to add still, and with the things I have added so far I've broken things and need to debug them. So there's still work to be done.

To learn if there's a new version of Axe released, there's a much simpler way than checking the thread manually. Go to the Latest Updates thread, and above the first post, click on the "Notify" button. All new versions of Axe will be posted in that thread, and the notify feature will send you an email the instant a post is made.

I hope to get 1.2.2 onto ticalc.org. With any luck, it should be one of the most stable releases since 1.0.0.

Activating zStart makes compiling like a russain roulette: you get a freezing unknown error with a 1/2odd.

Lastest version of Axe&zStart on a 2.43 84+

Hi, I'm not sure if this is a bug, but the command ->HEX seems to always point to the string "11" when used with axe fusion. Could you look into it? Thanks.

You are indeed correct. I don't actually remember doing this and I didn't record it in the changelog, but apparently I've already fixed this in my development version. So it'll be fixed in the next release. Until then, I guess don't use Axe Fusion if possible. Unfortunately, the system is still experimental and not super reliable, so issues like this seem to be common with it.

Activating zStart makes compiling like a russain roulette: you get a freezing unknown error with a 1/2odd.

Lastest version of Axe&zStart on a 2.43 84+

Can you elaborate? The frozen unknown error in Axe 1.2.1 is a known bug and should be fixed in the next version, but I can't quite understand the situation you're describing that led to it.

Yeah I noticed that but it's rare enough to make it acceptable, nut still annoying.
There's another issue : when compiling from Axe, the Goto function messes stuff up and leaks all your RAM so you have to RAM clear.

You mean scrolling to errors? Are you using an old version of zStart? I forgot to mention it in the changelog, but Axe 1.2.1+ now checks if zStart exists, and if so, uses its instant goto function for going to errors instead of Axe's. Unfortunately, the API instant goto function was broken in some older versions of zStart, but there's no way for Axe to easily know what version it is so Axe will blindly use the broken API function in older versions of zStart.