Axe Fusion should be fine for programs that you don't plan to release, but for now I would recommend not using it for released works. It's a very new and still experimental feature and I expect it to change in the future, and very possibly not retain backwards compatibility.

Quote from: bored_student on November 22, 2012, 03:17:32 am

couldn't you leave the parentheses

Code: [Select]

1=EXP1*2-1→Z
or if the "true" isn't always 1

Code: [Select]

0<EXP1*2-1→Z


Hmm, this didn't seem to work for me in my program. I guess Axe really doesn't support negative numbers in equasions. I figured out a different way to do it, and it works fine. Thanks for the help all!

What doesn't Axe support for negative numbers? Keep in mind that the normal, unsigned comparison operators mostly don't work for signed numbers, but there are the signed comparison operators: ==, ≠≠, <<, ≤≤, >>, and ≥≥.

I believe what you are looking for are the subroutines arguments, r₁-r₆. These are the polar equation variables, which can be found under VARS > Y-VARS > Polar...

Nope, the token hook definitely doesn't work for my AxiomDCS. I downgraded to Axe 1.1.2.

Also, a clipped line routine would be great for a later version of Axe.

Hmm... could you send me a copy of the Axiom so I can test it? I wouldn't rule out the possibility that I did something silly and created a bug that makes certain Axioms not work with token replacements.

And yes, I do have plans for a clipped line routine.

Found something in Runer's Axe 1.2.0 : token hook from axioms doesn't work anymore (I was really bored when I realized that FindFirst became 2-SampFZTest ).

In my quick test, it looks like they do work (see attached screenshot of MemKit token replacements). Make sure Axe's token hook is installed by opening and then closing Axe, and remember that for Axiom tokens to actually show up, the #Axiom(Name) line has to already exist in the program when you open it in the editor; adding it without closing the program editor will not work. Also make sure that the Axiom is an appvar and not a program, which is something that I forgot many times while designing Axioms. Either convert it to an appvar manually using something like Calcsys or compile a program that includes the Axiom.

If these steps don't fix the problem... well then we might have a bug on our hands.

---

Axe 1.2.0 breaks horribly Nymless v.93's new Main Menu animations.
You can try it for yourself, but be prepared to pull a battery.
Film at 11.

After a bit of debugging, it seems that when I tried to add proper rectangle clipping, I made a small mistake (that can result in huge errors). It's now fixed, but until I release Axe 1.2.1 which will contain this fix (hopefully soon!), I'd keep using Axe 1.1.2. Also, I'd be very careful using the X_1T, X_2T, Y_1T, and Y_2T variables now that they're special-use and their values may change without you realizing it! You can check the changelog for more info about this change.



A note to all Axe users: If a program you are developing has any chance of drawing rectangles at negative Y coordinates such that -Y=height, you will be affected by this bug in Axe 1.2.0. Please wait until the release of Axe 1.2.1 to upgrade.

Yay Only problem... I can't send stuff to calc anymore. Did the syntax change a lot?

What can't you send to your calc any more? And what linking software do you use? I was a little worried about the ability to send Axe itself because I changed it's header, but I checked and it still seemed to work fine for me with TI-Connect. I'm a little surprised that it has prevented you from sending other things to your calculator.

I seem to be having strange problems with an Invalid-Token error that pops up randomly

Is there any of discernible pattern at all? Fixing an error that pops up entirely randomly is nigh impossible, unfortunately. If it happens frequently when compiling one program, perhaps send it to me and I'll try compiling it over and over to reproduce (and hopefully fix) the error.

---

Anyways, I hope you guys like the new version of Axe! It did require a good amount of work, and a good amount of staring at existing code, but it seems that for the most part I could add a decent array of new features, and hopefully I successfully removed more bugs than I added! As for more updates down the road, I can't make any guarantees, but I hope that the next update will be a lot less than nine months after 1.2.0.

And remember, the Bug Reports thread exists for a reason.

Axe Parser
Omega 1.2.0

---

It's Thanksgiving, and this year, we can all give thanks for Axe living on! Just temporarily under new management.

New Features:

• Have the need for speed? Using #ExprOn will request that all following code and called Axe routines be optimized for speed instead of size! Using #ExprOff does the reverse. Currently this only affects a few Axe routines (*, Pt-On(), Pt-Change(), DrawInv, Horizontal+/-, >Hex), but more will come! Axe Fusion always uses the fastest Axe routines available.
• Continuing with the speed theme, DispGraphRecallPic has been added! It's the same as DispGraph and then RecallPic, but it's almost as fast as DispGraph alone.
• Fixed point division! Syntax is: /*
• Fixed point square! Syntax is: ²^r
• Labels and constant names can be up to 13 characters long!
• No longer corrputs the OS when unlocking flash!
• Even shinier commands list! BIG thanks to jacobly! I'm also trying to add size and speed data for everything; it's a work in progress, so please excuse errors/missing values for now.
• Full support for big endian variables.
• Signed min() and max(): just throw on an ^r.

Changed:

• Better string parsing, including spelling out multi-character tokens, more reliable "var", and "grp" (w) is now "tmp"; these arbitrary-size variables will be automatically deleted on exiting.
• Optimized most DispGraph variants: all but 4-level DispGraphClrDraw are smaller, which is larger because...
• 4-level DispGraphClrDraw is about 15% faster. Also, 4-level DispGraph is about 5% faster.
• Optimized >Hex, stdDev(), Horizontal-(EXPR), getKey(EXPR), ^-1, interrupts, and all archived variable routines slightly.
• Optimized more stuff that I forgot.
• nib{}^r now always reads from the half of memory your code exists in.
• inData(0,DATA) now returns 0, so no more adding 1 to all your key checks!
• ln(0) now returns -1, it seems slightly more proper than 255.
• Disp >Tok accepts the same argument type as Text >Tok.
• Added "signed" equal and not equal operators.
• Added optimizations for ^10, //0, and //-1, not that the latter two will ever be needed.
• The A-theta variables have been moved, so L₁ is now 768 bytes long by default.
• When pointed into a variable in RAM, the Y_1T and Y_2T variables will be updated automatically if the variable is moved.
• The X_1T and X_2T variables will act similarly when pointed into a VAT entry.
• The X_4T-Y_6T variables have been added.
• Slightly larger but faster multiplications by some large powers of 2.
• Fixed a bug when a string displayed in an app went offscreen.
• Fixed drawing sprites to arbitrary buffers.
• Fixed rectangle clipping.
• Fixed the size of the stdDev() subroutine.
• Fixed some Axe fusion-related bugs.
• Fixed some bugs with the token hook.
• Fixed some bugs with comments.
• Fixed some peephole optimization bugs.
• Fixed a silly typo in an error message.
• Fixed many errors in the command list.
• Fixed many other bugs that I forgot about.
• And probably introduced some bugs!

To quote the readme that should be included in the download:

TI-Boy SE is a Game Boy emulator (no Game Boy Color support) for the TI-83+SE, TI-84+, and TI-84+SE calculators.

If you've been trying Game Boy Color games, that might be why things weren't working.