Support
All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.
Forum closed
This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview 

AuthorThread
User

25.09.2008 12:36:46
2 behaviour sets
View

This posting is older than 6 months and can contain outdated information.
I created two separate behaviour sets with the construction kit. One for PLEX, the other for Slingplayer.

When I "compile, test drive" a set, it will install that set to the mapping but remove the other.

So for instance, If I compiled the PLEX set in BCK and then map all the buttons, then compile Slingplayer set, it will remove the PLEX set from the mapping screen.

Another thing that is happening is that it is creating two PLEX or Slingplayer icons in the mapping screen. I briefly asked this in another thread, and you told me to go remove it from the behaviour folder but this removes the wrong icon. I can not set the behaviours I created to the mapping icon which is left.

I hope this made sense. :/ 

These entries from the FAQ may be relevant to this topic:

Behaviours
User

25.09.2008 12:51:11
Re: 2 behaviour sets
View

This posting is older than 6 months and can contain outdated information.
Thanks for asking.

Remote Buddy tracks Behaviours by their identifier, not their filename.

So what did likely happen in your case is that both of your Behaviours 
share the same identifier. You can find that identifier in BCK > 
Behaviour Factory > Specifications and Metadata > Behaviour Bundle 
Metadata > Identifier.

Please make sure your two Behaviours have different identifiers. That 
way Remote Buddy can tell them apart and should show both of your 
Behaviours.

Extra Tip: 
By dragging an application directly onto the list in BCK > Behaviour 
Factory, Remote Buddy fills out all fields for your new Behaviour 
correctly and also makes sure that the identifier for your new 
Behaviour is unique to that application and isn't shared across 
multiple Behaviours.

Best regards, 
Felix Schwarz