Bug Reports

[Matrefeytontias]

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 ).

[Freyaday]

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.

[Runer112]

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.

[Freyaday]

How soon is 1.2.1 expected to be? A day or two, a couple of weeks? Months?

[Runer112]

I'm hoping that it will only take a week or two. I just don't want to release a new version with only one change, so it's really just a matter of how quickly bugs crop up and I fix them and how quickly I add new stuff.

[Matrefeytontias]

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.

[Hayleia]

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

Yeah, I agree, because the one I wrote is really unoptimized and I fear I won't be able to optimize it without breaking it

[Runer112]

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.

[Freyaday]

Are there plans for the sorely-needed white lines and rectangles?

[Builderboy]

On certain calc's, the key port needs to be written to with 0xFF before it can be changed reliably (or something like that, you might have to ask Calc84 or Thep or someone).  Either way, I do believe the Axe getkey(#) command needs a small upgrade to compensate for this.

[Freyaday]

Axe lets you include the same program twice.

[calc84maniac]

Axe lets you include the same program twice.

I would think that's a feature, unless it's recursively including the same program.

[Freyaday]

Axe lets you include the same program twice.

I would think that's a feature, unless it's recursively including the same program.

Why would you ever have any reason to include the same program twice?

[Builderboy]

Maybe you want to include the same code twice but underneath 2 different Realloc#() commands to modify the variables that the code modifies?  Either way I don't see any reason to remove the ability to include programs twice, as it doesn't really hurt anything.

[Hayleia]

Why would you ever have any reason to include the same program twice?

So you'll never include the same program twice, so the fact that Axe lets you include the same program twice is not a problem.
So I really don't get where is your problem