This posting is older than 6 months and can contain outdated information.
Hello Jake,
thanks for the info.
If you select only "Compile and testdrive", the addition of your
Behaviour to the menu is temporary and will be gone on next startup.
If you select "Export scripted Behaviour" and just confirm the file
dialog, Remote Buddy will save the Behaviour in its search path
permanently and it'll be available on next startup. As its really
just an export function, it does not add the Behaviour to the menu
right away, but rather just do what its labeld: export the Behaviour.
So:
- if you want to permanently add your Behaviour to the menu, use the
"Export" function
- if you want to testdrive it without restarting Remote Buddy, select
"Compile and testdrive".
- if you want to testdrive it without restarting Remote Buddy and
permanently add your Behaviour to the menu, make use of both functions.
The last option, which seems to be the most common one, too, will be
an entry of its own in RC2. You find all of the mentioned entries in
the BCK under "Behaviour Factory" when selecting your own Behaviour
and clicking on "gears" symbol on the lower, left side of the window.
Also, if you should be using a customized menu (Preferences > Menu),
Remote Buddy does not add entries to it itself, so if you add a new
Behaviour and you want it to show up as menu entry, you'll have to
manually add it. Remote Buddy's default menu will automatically
adjust, though. In either case, loaded Behaviours always show up in
Preferences > Mapping.
Hope that helps.
Best regards,
Felix