| Author | Thread |
User 29.01.2008 11:43:20 | temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. So, my fusion XHub/RB is coming together nicely now. Mapping everything to the virtual remote works perfectly, but with just one problem I need to solve... I know that the 'advanced' setting allows me to deactivate automatic activation of behaviours but is there a way to set this 'on-the-fly'? Or in other words, want I want to achieve is to force only the Xhub behaviour to remain active until manually deactivated. When I deactivate it, then I'd like behaviours to be automatically activated by RB again. E.g. it would be great if I could reach this 'advanced setting' from a RB context menu. Or was there perhaps an option to set, when compiling the behaviour, forcing it to remain active? I don't recall one, but it's been a few days since I've had chance to check. Cheers,
Rich
| 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.
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 29.01.2008 16:17:16 | Re: temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. Hello Rich, you can do what you want via Remote Buddy's AppleScript interface: 1) In the BCK, create two actions - one for activation, one for
deactivation 2) In these actions, make use of the behaviourcore command with the
respective code to "sticky" activate the Behaviour and return to the
auto-selection respectively. Sample code to be found in the
AppleScript dictionary in Script Editor and - if you need to get a
list of available unique identifiers - in the Remote Buddy FAQ. Best regards,
Felix Schwarz
| User 29.01.2008 16:52:16 | Re: temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. Cool! Thanks Felix, I'll check this out. I presume then I'd add these actions to my behaviour (with option 'do not include in menus'?) and they'd be implicitly called when activating/deactivating the behaviour? Thanks,
Rich
| User 30.01.2008 00:39:27 | Re: temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. So, I haven't managed to get this working, not sure what I'm doing wrong; Have defined an action called Activate which runs the following AS: tell application "Remote Buddy"
behaviourcore accessor "setSticky" stickyValue 1
end tell And one called Deactivate, which sets the value 0 In Behaviour Events I set "Activate" to run on Activation (all three events) and "Deactivate" on deactivation event. My behaviour is not "sticking" though. I tried adding the Actions to the menu, but they remain greyed out and unselectable. Maybe I need to explicitly say which behaviour in the behaviourcore command? Cheers,
Rich
| User 01.02.2008 14:03:01 | Re: Re: temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. You have two possibilities: 1) Tell Remote Buddy which Behaviour it should activate and mark sticky. F.ex. for EyeTV, this'd be: tell application "Remote Buddy"
behaviourcore accessor "setActiveBehaviour" identifier
"com.elgato.eyetv" with stickyValue
end tell 2) Tell Remote Buddy to mark the currently active Behaviour sticky: tell application "Remote Buddy"
behaviourcore accessor "setSticky" with stickyValue
end tell (yeah, AppleScript has an interesting syntax ;-) Remote Buddy's AppleScript dictionary has more info on the available
commands. Best regards,
Felix
| User 01.02.2008 14:20:17 | Re: temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. 2) Tell Remote Buddy to mark the currently active Behaviour sticky: tell application "Remote Buddy"
behaviourcore accessor "setSticky" with stickyValue
end tell Isn't that what I'm already doing (just with the difference of explicitly defining the value of 0 or 1)? I'm also slightly unsure as to when and how I should trigger this action? Ideally, I'd like to trigger it automatically as soon as the behaviour in question gets activated. I did however also try adding it to the behaviour's menu but it was greyed out (unselectable). Cheers,
Rich
| User 13.02.2008 10:13:01 | Re: Re: temporarily deactivating automatic behaviour selection | |
This posting is older than 6 months and can contain outdated information. Hello Rich, sorry for the late reply, I didn't see yours previously. You should assign the action to the respective event (at the top of
the mapping tab), wheras you should choose the right version of event
for the activation of a Behaviour. There're three - for manual
activation, for automatic activation (app is active application) and
for background activation (app is not active application, but runs and
it was indicated that it is of interest to the user to control it
nonetheless - f.ex. true for iTunes). Best regards,
Felix Schwarz
|
|
