| Author | Thread |
User 07.02.2007 08:24:49 | Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. I understand how powerful programming the behaviors in Xcode can be, and why that's a good idea and all.. But I haven't coded in quite a long time, and I'm basically coming to the table fresh.. And trying to figure out how to create simple actions is beyond me right now.. So I'm just wondering, why not have a system where a behavior can just call a menu item, like when you assign a keyboard shortcut in the mouse & keyboard pref pane.. So, for example, I want an action to go to the next image in Xee.. I would think there could be a system to just say "Next Image" or "Browse," "Next Image." I know this also can be done through AppleScript but I've never gotten the hang of AppleScript, and I can't really make heads or tails of the "Behavior Construction Kit" either.. Anyway, the product is really sharp, I just think don't think adding functionality to existing software is particularly simple right now.. -brian
| These entries from the FAQ may be relevant to this topic: Configuration 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
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 07.02.2007 11:34:01 | Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Hello Brian, thanks for sharing. In fact, the Behaviour Construction Kit is exactly what you are
looking for and makes creating your own Behaviours super-easy. It
allows you to create Behaviours within minutes. If you go to the
"Developers" page on the Remote Buddy website, you can watch a less-
than-5-minutes video that shows the creation of a Behaviour in its
entirety - including testing. Hope that helps. Best regards,
Felix
| User 08.02.2007 20:25:36 | Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Hey Brian, I'm a new user to Remote Buddy and while I have a some scripting in my background, I am not a programmer. I too was a little hesitant about using the Behavior Construction Kit. But after watching the example Quicktime I was able create my first working behavior in about ten minutes. I'll bet you can do it.
| User 09.02.2007 01:35:55 | Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. I'd like to use this thread to report a bug I've been experiencing with behaviours. I have a few scripted behaviours created and they seem to work fine. The problem is that when Remote Buddy is restarted, they become unrecognised. To get them working again, I have to open the Behaviour Construction Kit and manually choose the "compile and testdrive scripted behaviour" action for each of my scripted behaviours. Only then will my scripted behaviours be recognised or even show up in the mapping menu in preferences. After I do this, I can use my scripted behaviours again. Another problem related with this is that if I add those scripted behaviours to the menu, upon restart of Remote Buddy they will be replaced with an empty Behaviour folder menu item instead. Is anyone else experiencing this problem?
| User 09.02.2007 17:33:02 | Re: Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Hi, thanks for posting. That isn't a bug, that's a feature ;-) "Compile and testdrive":
Creates a complete Scripted Behaviour in a temporary location, then
loads it. That temporary location is not searched for Scripted
Behaviours on startup. "Export scripted Behaviour":
Permanently exports the Scripted Behaviour. By default, it suggests
the location Remote Buddy looks at for third party Scripted
Behaviours by default. Clicking Ok is basically all you have to do
here and it will be loaded on next startup. So, in short: if you click "Compile and testdrive", it is immediately
available, if you click "Export Scripted Behaviour", it will
automatically be available at every subsequent start of Remote Buddy. Hope that helps. Best regards,
Felix
| User 09.02.2007 17:49:02 | Re: Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Update: The next version will give you a menu item that will allow you to compile, testdrive and install a Behaviour in one go / with one click. Best regards,
Felix
| User 10.02.2007 00:09:27 | Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Felix: Export scripted behaviour doesn't work for me either. Or rather, even if I export the scripted behaviour, after restarting RB, my scripted behaviours will become unrecognised. I do see my scripted behaviours in ~/Library/Application Support/Remote Buddy/Behaviours/ - I also see the Camino and Google Video Player files. Those other two scripted behaviours are recognised but not the ones I make. Using RC1. | User 10.02.2007 13:04:02 | Re: Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Hmm .. since Remote Buddy has a version management system built-in that always uses the latest version of a Behaviour it can find online, in the Application Support subfolder or in its very own Application Bundle, chances are you are using a Bundle Identifier that is already in use by another Scripted Behaviour. What are the Bundle Identifiers and Versions of your Behaviours in
the Behaviour Factory > Specification and Metadata pane? You can also send me your exported Behaviours to have a look, if you
want. Just use the info @ the domain of this website address or the
form at http://www.remotebuddy.com/upload/ . Best regards,
Felix
| User 10.02.2007 14:38:32 | Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Felix: That was the problem. I was using the default identifiers, now that I've changed it to something else, it works the way you described. Thanks. One other thing since I have your attention... I have the menu (held) event globally mapped to "put computer to sleep". Sometimes when I use this and hold the menu button for too long, the computer will go to sleep for a second and then wake itself up. Can you do something to address this?
| User 10.02.2007 16:46:01 | Re: Re: Simpler behavior development? | |
This posting is older than 6 months and can contain outdated information. Thanks for letting me know. Regarding the problem:
What is probably happening is that your computer goes to sleep so
fast that it's already asleep when you release the button. Which, in
turn, makes the IR receiver create a HID event, which in turn, wakes
up the machine again. As a temporary fix: release the button promptly ;-) As a general fix: I'll add a delay of a second or two in Remote Buddy. Thanks for pointing out that problem! Best regards,
Felix
|
|
