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 

AuthorThread
User

03.05.2007 06:16:28
maybe a bug, maybe not

This posting is older than 6 months and can contain outdated information.
I've noticed something about the way RB sends keypresses. Let's say I set the up and down buttons on my remote to the up and down keys, and set the play button to the return key, and set the menu button to run the following applescript:

tell finder 
set Var to (choose from list {1,2,3} with prompt "pick a number" 
return Var 
end tell

This should open a dialog with three choices (the numbers 1, 2 and 3) and cancel and OK buttons (with 'OK' highlighted).

When this dialog is open, I can navigate the choices with the up and down keys, and the return key will press the 'OK' button.

With a Keyspan DMR remote with buttons assigned to keys as described above, the up and down buttons will navigate the dialog and the play button will click 'OK' - just as should happen, with those buttons emulating those keystrokes.

But with RB, the remote is useless while the dialog is open. I have to choose with the keyboard or mouse. Then, after the dialog is closed, all button presses that happened on the remote control finally get sent to the system.

(Mira acts the same way as Remote Buddy.)

Any reason why the keyspan DMR software can successfully emulate keystrokes when an applescript dialog is open, but RB cannot? It's kind of annoying. 

These entries from the FAQ may be relevant to this topic:

General
Hardware - Apple® Remote
Thread-display::