| Author | Thread |
User 01.05.2007 13:36:15 | Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. I have a minor issue with RC2 15b... What I'm seeing: - I'm using a Keyspan Front Row Remote
- I've mapped the Eject Key to run a custom action:
I'm using one Actor within the Action - an AppleScript
The Actor setting are:
Source code:
tell application "EyeTV"
activate
set current channel to "2"
set full screen to true
set playback volume to 1.0
end tell Execute on: Button press
Minimum delay between two runs of the script: (Checked) 3 s
- The script largely works as I'd expect it to What I expect to see instead: - Everything works as I expect, EXCEPT that, the 'Minimum delay' attribute of the AppleScript actor resets to the default settings if RemoteBuddy is quit and relaunched. The delay settings stick while RemoteBuddy is running. They only seem to reset to {Unchecked, 0.05 s} if RemoteBuddy quits. Final note: I love RemoteBuddy!
| 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.
Please update your copy of Remote Buddy to version 1.15 or later.
Hardware - EyeTV Receiver
The latest info on hard- and software-requirements including info on support hardware can be found on the dedicated page for EyeTV receivers.
Please consider making use of the free Remote Buddy trial version to test your device for compatibility directly on your computer.
| User 02.05.2007 13:01:01 | Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. Hello Robert, thanks for letting me know! It's actually a typo in the serialization routines that makes Remote
Buddy skip the timing info. Just fixed this. The fix will be
available with the next release. Best regards,
Felix
| User 06.05.2007 01:32:23 | Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. Is there an easy way of modifying the timing between runs value and the repeat delay value for all built-in behaviours? With Front Row's default mapping, up [held] is used to escape the current menu level - except that too often, I end up going two menu levels up because the timing between two rules is so set so low. | User 07.05.2007 14:27:01 | Re: Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. Oh, such an option wouldn't help here as FR support is weaved directly into Remote Buddy. It's absolutely certain the repeat rate is *way* to high for it,
though, once it kicks in. Shouldn't happen. The next release will
ignore all repeat events for the "menu level up" action (I just fixed
it right away). Best regards,
Felix
| User 08.05.2007 00:38:10 | Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. It's not just FrontRow, I also have the same problem in other applications. In Firefox for example, I have the left and right buttons set to go to the previous and next tab. Too often, I press a bit too long and it goes two tabs instead. Likewise, I have the play button mapped to close tab and I often close two tabs instead of one.
| User 09.05.2007 18:44:02 | Re: Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. This is specific to FireFox then (just tried). For all "old" (pre- RC2) keypress-based actions, a button press is always matched by a key press of the same length. With old versions and RC2 alike. Repeats are not sent. Only press and release events. FireFox, however, seems to do its own repeat timing here. Will be fixed with the next release. Any other place you noticed that? Best regards,
Felix
| User 11.05.2007 00:31:43 | Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. Vienna (news reader) is the only other place that comes to mind at the moment.
| User 11.05.2007 20:09:02 | Re: Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. There's no Behaviour for Vienna, yet, so I assume you've created one of your own ;-) Then, the fix is to simply set the Keystroke Actor in your Action to
only execute once on button press. It'll then ignore all subsequent
repeat and release events. Best regards,
Felix
| User 11.05.2007 23:53:22 | Re: Issue with RC2 15b, AppleScript Actors, and Minimum delay between runs | |
This posting is older than 6 months and can contain outdated information. Oops. That did the trick, thanks.
|
|
