Whoops, I was mixing up sub(B) with direct function calls like FName(B)

Does Axe 1.1.2 try to sign apps on calc? Because I tried to send a app to my computer (compiled with 1.1.2) and it kept giving me an error about a bad signature.
I then downgraded to 1.0.5 and it send just fine.

Is this code supposed to fail?  Throws an Err: Bad Constant for me

[00]->Str1
Str1->Str2

Quote from: thepenguin77 on February 20, 2012, 03:58:26 pm

I found an error in the way the token hook is handled. When you copy the text string to ram, I noticed that you don't actually configure the first byte of the string. Since most of the tokens end up being somewhere in the 01xx range, the first byte of the ram string is 1.

But here's the problem. On closer analysis of how this hook works, that first byte actually means something. The format looks like this:

[Key code][length of string][string]

Where key code is the actual key you press to signal the token. As you can see, the key codes you are returning are incorrect and then that leads to all sorts of problems. (01 translates to right, when you use axe tokens in a Recall queue, the calculator hangs because tokens aren't actually being inserted)

So the simple fix is just to put the proper key codes in. The quickest way to get the proper key code is to simply put the token in DE and call _GetKeyPress, that will return the proper key in A.


Edit:
    If you are going to call _GetKeyPress from within your hook, make sure you temporarily disable the hook. Otherwise you're going to have fun with recursion.

Can you elaborate on this problem? I haven't noticed any problems with the hook in my testing of it. And I can't seem to cause any problems by recalling strings that contain Axe tokens or by entering Axe tokens into the recall prompt.

I always forget to check this thread.

I believe the problem is only evident if you recall the tokens with the recall queue in internal mode. When this happens, the recall queue goes through each token, looks up its appropriate key, and sends that press to _cxMain. It does this until editCursor == rclQueue. The problem is that Axe doesn't provide the correct keypress for each token (and I don't blame it since this has never been documented before) so what happens is that _cxMain gets bogus keypresses which either cause the incorrect token to be input or the recall to hang (if a right arrow was being passed for instance)

I would guess that the reason you can't emulate this is that the OS uses external recalling because it would simply place all the appropriate pointers in ram at whatever place the variable you wish to recall starts at. Now, CatalogHelp won't let me paste to any context but the homescreen, but I would guess that if it would let me paste when the Axe token hook is in place, it would fail.

Edit:
   Lol, it's far too late at night. The ways I form sentences are clearly visible in my repetition of words.

Edit2:
    Boom

Found an end-of-file bug. If the last line in a source program is Return (followed by any number of spaces) followed by a one-byte token, the one-byte token is ignored.

Update to the newest Axe and find out :] Tech support for older Axe versions unfortunately usually amounts to updating to the newest Axe before any more tests are made.  I do know that a lot of bugs were fixed in the newest version, so there is a good chance that your problem could be fixed by updating, but in the event that it doesn't, post again and we will sort everything out ^^

Hmm. Weird stuff, will post my breaking code then.

Using Files in Copy() is broken, you have to add 12 to get them to work as expected.

Edit: nvm, it was the program header, and the offset circumvented the proglem.  ignore