the actual code depends on what you want your menu to do. should it take up the whole screen? should it only show up on a smaller section? should it scroll smoothly? should the selector move or stay in place?

you'll be a lot better off if you write the code yourself, as you can choose exactly how you want it to look and you'll end up learning things in the process that you'll absolutely need when writing anything more complex. the basic idea, though, is to have a list of names. if you want the selector to be able to move on its own, you will then need two values, one for indicating the offset to the first item that's on the screen and one indicating the current position of the selector. then adding those two values together will give you the offset in the list to the currently hilit menu option. if you want the selector to be stationary and have the menu options scroll behind it, then you only need one indicator, the offset of the item currently hilit.

i know that may sound a bit complex, but if you can't figure that much out on your own you'll have a very hard time writing anything substantial, so give it your best shot =)

I already gave you a code on Cemetech that produces a menu similar to the ones you use in Basic. I copy-paste it here if you want.
The only thing that interests you is the MENU routine (and the CursorForMENU routine that is needed for the first one to work), the rest being some example code to show you how to make it work.

Where in Basic you would have written this line:

:Menu("TITLE","OPTION_1",Label_1,"OPTION_2",Label2,...,"OPTION_N",Label_N)

Just write those two lines in your Axe code:

:MENU("TITLE"[00]"OPTION_1"[00]"OPTION_2"[00]..."OPTION_N"[00][25])
:Z-Test(,Label1,Label2,...,LabelN)

Now the code in itself:
.MENU

.###########################
. PRELIMINARY COMMANDS
.###########################

Fix 5
ClrDraw

.###########################
. MAIN CODE
.###########################

MENU("TITLE"[00]"OPTION_1"[00]"OPTION_2"[00]"OPTION_3"[00]"OPTION_4"[00]"OPTION_5"[00][25])
Z-Test(,Label1,Label2,Label3,Label4,Label5)

Lbl Label1
Text(0,,"THIS IS THE LABEL 1")
DispGraph
Pause 3600
Return

Lbl Label2
Text(0,,"THIS IS THE LABEL 2")
DispGraph
Pause 3600
Return

Lbl Label3
Text(0,,"THIS IS THE LABEL 3")
DispGraph
Pause 3600
Return

Lbl Label4
Text(0,,"THIS IS THE LABEL 4")
DispGraph
Pause 3600
Return

Lbl Label5
Text(0,,"THIS IS THE LABEL 5")
DispGraph
Pause 3600
Return

.###########################
. SUBROUTINES
.###########################

Lbl MENU
Text(0->r3->r2,,r1)
While 1
End!If {stdDev(r1,r2++)}-37
RectI(0,,96,6)
For(r2--)
 Text(0,r3++*6,r3>Dec)
 {|E86D7}-2->{|E86D7}
 Text ": "
 Text stdDev(r1,r3)
End
0->r1
While 1
 r1+getKey(1)-getKey(4)+r2^r2->r1
 CursorForMENU()
 DispGraph
 Pause 200
 CursorForMENU()
EndIf getKey(9)
Returnr1

Lbl CursorForMENU
RectI(0,r1+1*6,6,)
Return


The >Dec is not a ">" followed by "D" then "e" then "c" but the token you can find in the Maths menu when editing an Axe program (the second token in the list).
Sorry, I used TokenIDE to write and test that code so I did not have it written as "►Dec".

And is "r3" the token you find in "Vars", "Left", "3", "3" and not just a "r" before a "3" ?

Ah, the "|E" is not a "|" followed by a "E", but the small uppercase "E" you find with [2nd]+[,]

Especially in Axe, though, some really impressive menus can be made, if some time and effort is put into it. For instance, this one here:

(cue comments that the fire thing is overused by now )

In any case, I can see that that might be unsuitable for an inventory screen, but deviating from the standard OS menu is likely a good idea in this case. For instance, using 5*3 font instead of the 7*5 would allow you to have more menu items available on the screen at a time

Plus, it encourages you to experiment and get more used to Axe. All in all, a win-win situation.