| Author | Thread |
User 16.10.2006 14:27:18 | "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. I bought Remote Buddy to use on my Mac based media centre, and it works a treat, thanks! The only thing that niggles me is that to launch something (for example Front Row), you navigate to that menu item and select 'Activate Behaviour' to launch that application. Is that right? I find this term/language unintuitive, especially for the rest of the family to use. Is there a away to change this menu item to say, for example, 'Launch FrontRow' or just 'launch'? Even better, that selecting 'Front Row' from the applications list just launches? Or have I misunderstood what 'Activate Behaviour' means?
| These entries from the FAQ may be relevant to this topic: Behaviours
There are several possible error sources:
- The application has been installed after Remote Buddy has already been launched
For efficiency reasons, Remote Buddy only searches for supported applications when its started. If you have installed an application after launching Remote Buddy, please quit Remote Buddy and launch it anew.
- Oudated program versions
The installed version of the program in question could be outdated and identify itself with a different Bundle Identifier than the version supported by Remote Buddy. This problem often occurs with Mplayer OS X. The most recent version of that application is not to be found on Sourceforge but on directly on the pages of Mplayer HQ.
- Custom menus
If you use a custom menu in Remote Buddy and you don't make use of Remote Buddy's smart folders, the menu structure is static. You have to manually add the behaviour into a place of your choice in the menu.
- The behaviour is deactivated.
Make sure, the checkbox in front of the Behaviour's name in the Mappings pane of the preferences is active.
- The Launch Services database is outdated.
Remote Buddy uses Launch Services to check for the availability of an application on your Mac. If the Launch Services database of OS X is incomplete or outdated, so is Remote Buddy's dynamically created menu. The solution, though is easy. Download LSRefresh, launch it, select the application(s) that don't turn up in Remote Buddy's menu, wait until the update is finished and then restart Remote Buddy.
General To navigate the menu, you can use the following button presses:
"Left" - up by one level in the menu
"Right" and "Play" - choose the current entry
"Left hold" - go to the main menu
"Plus" and "Minus" - scroll through the entries
"Menu hold" - jump to the first entry of the current menu
"Menu" - fade in/out the onscreen menu
Hardware - Apple® Remote
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.
| User 16.10.2006 15:00:02 | Re: "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. Hello Jonathan, thanks for asking. First, a short explaination from the web site as to what Behaviours are: Behaviours link Remote Buddy with its environment. They are the links
that allow Remote Buddy to control other applications and perform
special actions. Ok, so basically, Behaviours can contain any functionality. They can
do much more than only tightly link applications to the input of your
remote. Ejecting CDs or adjusting system volume like the Audio & CD/
DVD behaviour is doing is just an example for this. That's why the
term behaviour and not application is being used, as application
would be more restrictive and certainly confusing for more
specialized stuff like what the Audio & CD/DVD behaviour is doing. However, if you want to change any occurence of "behaviour" to
"application", all you have to do is do a Find / Replace on Remote
buddy.app/Contents/Resources/English.lproj/Localizable.strings and
pay attention you save the changed file in UTF-8 encoding. Behaviour
will still turn up in the "normal" Remote Buddy windows, though. Best regards,
Felix
| User 16.10.2006 15:32:42 | Re: "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. OK, I think I understand a bit better. So it isn't actually the same thing as launching an app?
| User 16.10.2006 19:30:02 | Re: Re: "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. It often ends up to be similiar - but not always. Technically speaking, Remote Buddy tells a behaviour that it is now
the active behaviour. The behaviour can then decide what it wants to
do to finish its setup. In most of the cases, this is to look for a
running copy of an app or launch that app if it is not already
running. But it could be something totally different. In the Audio & CD/DVD behaviour, for example, it just sets up some
required system structures to offer best performance during its use
lateron. Since a behaviour can do anything in its setup routine, using the
"launch" verb would not always be appropriate - while "activate"
always is. Best regards,
Felix
| User 16.10.2006 21:34:55 | Re: "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. Right! Thanks for the explanation Felix, I get it now!
| User 17.10.2006 11:10:20 | Re: "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. How about allowing the creator of a behaviour to name it appropriately? Thus, most behaviour creators would name it "Activate iTunes" or something like that
| User 18.10.2006 18:55:02 | Re: Re: "launch ....' instead of 'Activate Behaviour'? | |
This posting is older than 6 months and can contain outdated information. I may think about it. Yet, every customization is two-folded: Pro:
- the creator can tweak one more thing Contra:
- behaviours could get too bloated to really make creating them as
simple a task as it is right now.
- localization
- any additional feature may as well introduce limitations for future
extensions So for now, I don't plan to add it, although technically it's not too
much of a problem. Best regards,
Felix
|
|
