There are built in commands to do this; rotC( is ShadeNorm(), and rotCC is Shade_t(). Note, however, that these are not recursive functions, so you can't chain them (like rotC(rotC(Pic1))).

Thanks for the help, I have another question. How can you check your battery in axe? Like how much you have left?

From Xeda's opcodes

Smart Battery Check
EF6F4C3D280A78FE1E
EF21521808
EFB3503E042001AF
EF8C47EFBF4AC9
This is my BSA (Battery Status All) program. If you are
running an 83+, a value of either 0 or 4 is stored in Ans. If
you are using an 84+, a value from 0 to 4 is stored to Ans. 0
is the worst and 4 is the best. To be clear, 2 (meaning your
batteries are okay) is a possible output if you are using an
84+.

(of course, add the Asm() commands in front of each hex code line, or put them all in one line and put an Asm in front of that line).

you CAN do other things while running the Input command if you use interrupts. interrupts do exactly what they sound like; they interrupt whatever code is running at regular intervals in order to run something else before returning you back to your previous position to continue running there. it isn't too difficult to manage in axe, and the documentation explains fairly thoroughly, so i won't go into more detail.

if you want to display this during normal homescreen operations, though, then the problem becomes more difficult. i think it could be managed with a somewhat hackish combination of hooks (something like using the cursor hook for a makeshift timer to update your battery icon periodically and then using the homescreen hook to redraw it whenever the screen has been updated). i'm not the person to ask about how to manage this, how good it would look, or if it's even possible, though .

like i said, look in the included documentation for whatever version of axe you downloaded. basically, though, all you have to do is set the interrupt frequency (how often the subroutine will be called) and destination (the name of the subroutine to be called) with
fnInt(LBL,FREQ)use
FnOnto enable the interrupt when you want it running, use
FnOffany time within your code when you want to temporarily disable them, and
LnReg^rbefore exiting your program to disable the interrupts and clean things up again for the os.

EDIT: also, these interrupts are fired VERY rapidly, much more rapidly than your battery icon need be redrawn or any battery checking need to be done. for the best results on this project, you should set frequency to 6 (the highest number allowed. higher numbers indicate a lower frequency because it's talking about the duration between interrupts, so i guess "period" would probably be a better description than "frequency" for this field) and then only check once out of every several times the subroutine is executed or (if you're running on a model with crystal timers), use those and (check the battery|update the battery icon) only every second or so.

fnInt(NAME,6)

FnOn
Repeat getkey(15)
input
End

LnReg^r

Return

Lbl NAME
<interrupt code goes here>

The input command gives full control to the OS, so custom interrupt will be disabled. The only way to alter the functionality of input is with hooks, which are difficult enough to coordinate properly in assembly and not supported Axe features.