0 Members and 3 Guests are viewing this topic.
In other news, Frey continues kicking unprecedented levels of ass.
If (X=0 And (Y>5)) Or (Y=16)
If ((1) And (0)) Or (1)
If A=/=0 and (B=/=0
If X=0 and (Y>5) or (Y=16)
Another thing I added was the ability to stack Fix commands. So "Fix 135" is the same as "Fix 1:Fix 3:Fix 5". Also, there is now a fixed jump table built into the app so hopefully applications like DoorsCS and zStart can take advantage of using some useful Axe features externally once I release the API.
getkey(key1,key2...)This would check all of the keys with the corresponding getkey numbers and return the getkey number of the one that was pressed.
The Axiom system is great. Things like automatic jump and call replacements and manual 16-bit load replacements are great, which even the hard-coded Axe commands cannot do. But there's one thing that internal Axe commands can do whereas Axioms can't that I would love to be able to do. Would it be possible to add a new internal Axiom compiler feature that allows calls to be made with offsets? Perhaps a new macro like ld b,b \ .db BYTE \ .org $-2? Because this would be incredibly useful for calling a command in slightly different ways, like you often use with an optional buffer argument for drawing commands.
calc84manic: It would return the first value in the listRuner112: Instead of having to check if getkey (not getkey()) is part of a list of accepted values and then do getkey->VAR, you'd do getkey(list) and get the same speed and keyholding abilities of getkey()
Data(key1,key2,key3,...,keyN,0)-1->AWhile {A+1->A}->BEndIf getKey().B now holds the resulting key or 0 if none match