Support > Remote Buddy Forum > Creating a behaviour to run scripts // 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

24.03.2010 13:44:05

Creating a behaviour to run scripts

View

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

I have a couple shell scripts (that I can easily wrap in or port to AppleScript) that aren't really associated with an Application, but that I want to be able to fire off using remote buddy.

I'm totally new to Remote Buddy, but after several hours of banging my head against the wall, I've been unsuccessful in figuring out how to do this. I can kind of do what I want if I create a new custom action off an existing behavior, but I can't figure out how to have a behavior that's just for this purpose. I don't really want to have to activate some other app to run the script.

Any advice?

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.

Configuration

How do I add a new action to a Behaviour - f.ex. an emulated key press or AppleScript? (FAQ015E0153)
1) Open the Remote Buddy Preferences via the pulldown-menu and choose "Mapping".
2) Choose the mapping you want to modify.
3) Select "Custom actions" for the button you want to map to an action of your own.
4) Create the action you need using the appearing editor.

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.
After updating to OS X 10.6.2, my Apple® Remote is no longer available for selection in Remote Buddy. (FAQ015E0236)
Please update your copy of Remote Buddy to version 1.15 or later.

User

24.03.2010 13:59:36

Re: Creating a behaviour to run scripts

View

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

Thanks for asking.

You have several possibilities:

1) Check the "Globally available" checkbox for the respective actions in the Custom Action Editor (=> in Prefs > Mapping > [App of your choice] > "Custom actions" entry in popup) and you can select and use that action anywhere. The application controlled by the Behaviour you added this action to doesn't need to be running.

2) Add it in the Behaviour Construction Kit > Action Factory and check the "Globally available" checkbox. Your action now becomes available everywhere (in the "Misceallaneous" category at Prefs > Mapping and at Actions > Miscellaneous at Prefs > Menu)

3) Create your own Behaviour using the Behaviour Construction Kit > Behaviour Factory, mark your action to be globally available and add your action to the newly created Behaviour. Then make sure the metadata is set correctly, so it doesn't depend on any particular application, compile, testdrive and install it. Just like in 1), you can now access your action everywhere in Remote Buddy, filed under the name of the Behaviour you created.

For step by step instructions, please see the Remote Buddy Help > How To section.

Best regards,
Felix Schwarz

User

24.03.2010 14:36:53

Re: Creating a behaviour to run scripts

View

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

Thanks for the advice.

In reading your response and going through the documentation again, I realized the source of my stumbling block.

I neglected to realize creating my own profile menu would give me more control. I was trying to use the built-in menu and just couldn't get it to do anything I wanted to.

Thanks again, I'm sure I'll have more questions as I delve deeper into the capabilities of your fine product.

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