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

12.10.2007 21:08:02
Re: Re: Many problems and suggestions to RB 1.7

This posting is older than 6 months and can contain outdated information.
 
About 6)

I made a screenshot of the right scan key on the PS3 remote. An 
image is worth a thousand words :-) You can access it on:

http://token.no-ip.com:8000/~andre/rb/ps3-scan-right-button.png

 
Thanks. Fixed it right away now.

About 7)

I'm sure I chose the "Left double click". I mapped the ENTER, X, 
triangle, box and circle to be each one of (respectively): click, 
scroll on/off, double-click, click-and-hold and right-click. The 
only one that does not work as expected is double-click.

 
Just checked, I'm using "Left Double Click" for sure.

 
I couldn't find any problem with it under 10.4.8, 10.4.10 and 10.5. 
The emulated clicks are really short, though (1/100 sec). The next 
version will have clicks with a 1/10 sec length.

Updated to 1.7.3. The iTunes problem is still the same. To reproduce 
it: Stop iTunes manually (using your mouse). Bring on the RB menu 
and start iTunes behaviour (that will also start iTunes). Open the 
menu again, go down to the Quit option, and press enter/play. iTunes 
will close and open again. Repeat.

 
This should finally be fixed in 1.7.4 now.

12) I had RB on the menu only. After upgrading, it started apearing 
on the dock + menu, even if the options still indicated it should be 
only on the menu. I had to change to dock only + restart + menu only 
+ restart to get it back only on menu. That as from 1.7 to 1.73 
(didn't pay attention on this on the last upgrade).

 
Thanks for reporting. This is a known problem.

Best regards, 
Felix 

Thread-display::