personalized menu

[tigger]

If I made a personalized menu in the home Directory could I make another different personalized menu in every subdirectory of HOME? Does the personalized menu in the subdirectory influence the menu of HOME-Directory? How?

[Raymond Del Tondo]

(09-03-2015 08:40 AM)tigger Wrote:  If I made a personalized menu in the home Directory could I make another different personalized menu in every subdirectory of HOME?

Yes.

Quote:Does the personalized menu in the subdirectory influence the menu of HOME-Directory? How?

No, but if you have a custom menu (which you call "personalized menu") in the current subdir, that one will be shown when pressing CST, so it will override the custom menu in HOME.

This is valid for the HP 48 Series.

[tigger]

thanks, I guess it means:
Whenever I am in a subdirectory I see the "custom" of the subdirectory.
Whenever I go to home I will see the "custom" of home.

The two different "custom's" can exist at the same time.

[Dave Britten]

You can also have "nested" custom menus that lead to one another. Store your default custom menu in 'CST.DEF', then store the name 'CST.DEF' into 'CST'. (Referencing it like this prevents the MENU command from accidentally blowing away the contents of the menu; just put 'CST.DEF' back into 'CST' to recover).

Then store additional custom menu definitions in other variables - I've got 'CST.BASE' for base operations, for example - and have your main custom menu pull them up via 'CST.BASE' TMENU.

[tigger]

Does it mean you make Kind of a tree of this personal menus?
Do you have short example? Is there anything easy to read about in the net?

You mean you build `CST.DEF`in the home menu. In there you safe other menus of subdirectories?

[Dave Britten]

Yeah, it's pretty much a tree. The main custom menu, i.e. the one you get when you press the CST key, is stored in 'CST.DEF' (you can use any name you like, really). Then store the name 'CST.DEF' into 'CST'.

From inside that menu, you can have small programs assigned to the keys that invoke other menus with TMENU. Here's my home dir custom menu setup from my 48SX. The 48 manual explains the structure of custom menu assignments if it isn't clear what's going on here.

CST.DEF:

Code:

%%HP: T(3)A(D)F(.);
{ { "BASE"
\<< 'CST.BASE' TMENU
\>> } { "CHARS"
\<< 'CST.CHARS' TMENU
\>> } { "DIRS"
\<< DIRS
\>> } % %CH "\GS" {
"CLFIN"
\<< { FV I%YR PMT PV
N PYR } PURGE
TVMEND
\>> } }

CST.BASE: (PEEKBASE and ALLBASE are external programs.)

Code:

%%HP: T(3)A(D)F(.);
{ { "HEX" { HEX
\<< { HEX } PEEKBASE
\>> } } { "DEC" { DEC
\<< { DEC } PEEKBASE
\>> } } { "OCT" { OCT
\<< { OCT } PEEKBASE
\>> } } { "BIN" { BIN
\<< { BIN } PEEKBASE
\>> } } { "ALL"
ALLBASE } R\<-\->B AND
OR XOR NOT { } R\<-\->B
}

CST.CHARS:

Code:

%%HP: T(3)A(D)F(.);
{ "" "!" "#" "$"
"%" "&" "'" "(" ")"
"*" "+" "," "-" "."
"/" ":" ";" "<" "="
">" "?" "@" "[" "\\"
"]" "^" "_" "`" "{"
"|" "}" "~" "" "\<)"
"\x-" "\.V" "\v/" "\.S" "\GS"
"\|>" "\pi" "\.d" "\<=" "\>="
"\=/" "\Ga" "\->" "\<-" "\|v"
"\|^" "\Gg" "\Gd" "\Ge" "\Gn"
"\Gh" "\Gl" "\Gr" "\Gs" "\Gt"
"\Gw" "\GD" "\PI" "\GW" "\oo"
"\161" "\162" "\163" "\164" "\165"
"\166" "\167" "\168" "\169" "\170"
"\<<" "\172" "\173" "\174" "\175"
"\^o" "\177" "\178" "\179" "\180"
"\Gm" { "PARA" "\182" }
"\183" "\184" "\185" "\186" "\>>"
{ "1/4" "\188" } {
"1/2" "\189" } { "3/4"
"\190" } "\191" "\198" "\.x"
"\O/" "\222" "\Gb" "\230" "\:-"
"\254" }

[tigger]

What I understood is,
there is the "main" CST.DEF which contain CST.BASE and CST.CHARS.

First you might go in the menu CST.DEF. From there you could call besides other menus the two menus CST.BASE and CST.CHARS.

Could you help build such a tree with only three element in every branch. It might help me to understand how this tree "works".

[Dave Britten]

(09-03-2015 03:00 PM)tigger Wrote:  What I understood is,
there is the "main" CST.DEF which contain CST.BASE and CST.CHARS.

First you might go in the menu CST.DEF. From there you could call besides other menus the two menus CST.BASE and CST.CHARS.

Could you help build such a tree with only three element in every branch. It might help me to understand how this tree "works".

There isn't much to it, really. Assuming you understand the basics of setting up a custom menu, which is nothing more than a list of whatever you want to appear in the menu, you include labeled items which run a small program like \<< 'CST.BASE' TMENU \>>, and then pressing that key takes you to the appropriate menu.

e.g.

Code:

{ { "BASE" \<< 'CST.BASE' TMENU \>> } } 'CST.DEF' STO
'CST.DEF' 'CST' STO

That would create a custom menu with a single item labeled "BASE", which calls up the menu stored in 'CST.BASE' (which is, again, just another list of whatever you want in the menu).