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

12.09.2010 15:16:11
Behavior Not activated
View

This posting is older than 6 months and can contain outdated information.
I want to create a behavior which has no associated application and upon activation (by nintendo button 1) will initially activate Front Row (and later provide other functions) , so here's what I did.

1. Add New Behavior: 
Name: My Behavior 
Menu Address: my.behavior 
(All application recognition options are not selected)

2. Events 
on Manual, Auto-Front, Auto-back 
- Activate/Deactivate Front Row

3. RVL-CNT-01 Mapping 
Button 1: Activate / Deactivate My Behavior

4. Compile and Testdrive Scripted Behavior

5. Just to be sure the key is mapped, in Global Mapping 
- RVL-CNT-01 Mapping 
- Map key 1 to "Activate / Deactivate My Behavior"

6. Press button 1 on Nintendo, expect "My Behavior" to be activated and then "Front Row" to be activated but nothing happens at all.

Have done this several times and pretty sure I have not made any typo errors.

What am I doing wrong ??

Thanks

PeterC

 

User

19.09.2010 07:25:36
Re: Behavior Not activated
View

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

I want to create a behavior which has no associated application and upon activation (by nintendo button 1) will initially activate Front Row (and later provide other functions) , so here's what I did.

1. Add New Behavior: 
Name: My Behavior 
Menu Address: my.behavior

 
This isn't a valid address. It should always start with top. I recommend using top.applications.

What's also important (at least when you create more than one Behaviour) is that each Behaviour's unique identifier is actually unique.

2. Events 
on Manual, Auto-Front, Auto-back 
- Activate/Deactivate Front Row

 
A few notes: 
1) What do you want to achieve? 
2) Since your Behaviour is not associated to an application: 
a) the events auto-front and auto-back will never occur for your Behaviour. 
b) it'll not stay activated unless you create an action that makes the selection "sticky" and that's invoked for the "Manual activation" event. It'll then stay activated until you explicitly select "Deactivate" from the Remote Buddy menu. The AppleScript source code for this is (replace com.your.behaviour with the unique identifier of your Behaviour):

tell application "Remote Buddy" 
behaviourcore accessor "setActiveBehaviour" identifier "com.your.behaviour" with stickyValue 
end tell

If that doesn't help, please feel free to send me a copy of your Behaviour to the info address from the imprint of this website and I'll have a look. Please include a description of what you want to achieve with your Behaviour.

Best regards, 
Felix Schwarz