#91 Custom buttons (or menu items) in wxCatapult (or OSD)

[Patrick van Arkel]

I would like to see custom buttons in catapult. These
buttons must be used to assing TLC script 'functions' to
them. Just brainstorming again.

[Manuel Bilderbeek]

Similar idea for OSD menu:

<Wolf_> you know what I would like, a menu in the OSD where I can put/record complete commands
<Wolf_> and give these commands short names, like "RecChn FMPAC start" and "RecChn FMPAC stop"
<Wolf_> without doing TCL crap, just built-in command storage
<Quibus> and you would have to type those commands?
<Wolf_> once, to store them into a slot
<Wolf_> that could be a commandline thing btw
<Wolf_> something like:
<Wolf_> recordmacro <slot> <command>
<Wolf_> where command could be 'record_channels start PSG'
<Quibus> then you can just as well type the Tcl command directly
<Wolf_> don't want
<Wolf_> want in menu :P
<Wolf_> once
<Quibus> well, feel free to code it :P
<Wolf_> to record it into a slot
<Wolf_> after that, I'll use the OSD
<Quibus> if you name your proc "toggle_MYNAME" it will end up in the Toys menu
<Wolf_> Don't want it into the toy menu
<Wolf_> I prefer a Cmd menu in the root of the menu :P
<Wolf_> recordcommand <slot> <command> <commandname>
<Wolf_> recordcommand 1 "record_channels start PSG" "RecChn PSG start"
<Wolf_> that would be nice :D
<Wolf_> I can imagine handhelds can benefit from it
<Wolf_> like putting all the commands you actually need into the OSD
<Quibus> There are no keyboards on handhelds to type stuff :-)
<Wolf_> you can define these menus @ PC and put them into the handhelds
<Wolf_> as these OSD schemes are stored in a file

[Anonymous]

Needs more info.