Support > Remote Buddy Forum > Adding contsructed behaviours // IOSPIRIT [EN]

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

Author

Thread

User

23.10.2015 16:16:17

Adding contsructed behaviours

View

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

I followed the help docs to create a new behavior and everything worked well until the last step - "Once you have finished development, select "Compile, testdrive and permanently install Scripted Behaviours" but after doing this the behavior does not install, the only way to run it is compiling and testdriving.
I can export/install an .rbbehaviour from ~/Library/Application Support/Remote Buddy/Behaviours/ but still does not show in the list of available behaviors.

Is there another step involved not mentioned in the how to guide?

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

Behaviours

How can I create my own Behaviours? (FAQ015E0240)
You can create your own Behaviours with the Behaviour Construction Kit. A video on the Remote Buddy website provides you with an overview and step by step instructions.

You can also find step by step instructions in the Remote Buddy Help under "How Tos". You can access the Help via Remote Buddy's icon in the menu bar and via the support area of this website.

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs