This posting is older than 6 months and can contain outdated information.
It depends on what you want to do. If all you want is to create one Behaviour per device you want to control, the correct approach is to not associate the Behaviour with any application, but instead create an extra action and assign it as action to execute when the Behaviour gets activated. That extra action should contain an AppleScript actor with this code - which will make your Behaviour remain active until you explicitely choose another Behaviour:
tell application "Remote Buddy" to behaviourcore accessor "setSticky" with stickyValue
Once that action is created, you can reuse it in all your Behaviours.
Great... thanks for the tip. What application (if any) should I associate the constructed DVD behavior with? I think I remember needing to associate it with RB in order to get it to work when I was testing. Maybe I should create an applescript app that runs while i'm controlling the DVD player... any thoughts?
You don't necessarily need to associate a Behaviour with an application. However, if you don't, be sure that the option "this behaviour requires this application" at Behviour Factory > Specification and Metadata is not ticked. Your "application-less" Behaviour will not be loaded otherwise.
Hmmmmmm.... any chance that an API like that could be in a future release?
I'm sorry, but I generally can't comment on future releases and development.
Best regards,
Felix Schwarz
