RasPlex rc3 - mouse problem

Hey Guys..

 

Installed the latest RC3 on rasberry modell b.

 

Tried both wireless and cable mouse, but nothing works. When Im running XBMC on same device everything works great. Is there something im missing ?

Dont have a CEC remote available at the moment, and just want to run the setup.

 

Thanx!

Hey Guys..

Installed the latest RC3 on rasberry modell b.

Tried both wireless and cable mouse, but nothing works. When Im running XBMC on same device everything works great. Is there something im missing ?

Dont have a CEC remote available at the moment, and just want to run the setup.

This problem is not specific to RasPlex. It's a problem with all implementations of "Plex Home Theater" on all existing platforms (ie: Windows, OSX, Linux).

The PHT developers flatly refuse to implement mouse support, with the (very 'tired') argument that PHT is intended for '3-foot interface remotes' with a TV... ONLY !!!

A vast group of users disagree with them on that point (myself included as you probably deduced already ;) ), but that doesn't change their position on this.

Since the source code of the GUI for the official PHT versions is inherently incompatible with mouse usage, RasPlex automatically inherits that incompatibility in porting the sources to the RPi.
 

There are two good solutions to the problem. One is to use some universal IR remote (may require some custom configuration though), but the easiest method is to connect any standard USB keyboard. I use a miniature USB keyboard myself, connected to the RPi by an RF dongle (just a USB connector plug), but a full-scale USB keyboard with normal USB cable works just as well (though less convenient to have in front of the TV).

Edit:

It's possible to patch one of the PHT files so as to make it respond to mouse input, but the response of the PHT GUI to such mouse input is both illogical and inconsistent, especially in the main menu. XBMC also has illogical mouse response in the outermost main menu as well, since the menu entries can move in direction opposite to the mouse movement, which is a bad problem with vertical main menu skins in particular. This is also where PHT inherited its worst mouse misbehaviour from. The big differences are that XBMC's mouse response in most submenus is fine and that the mouse pointer is visible, which is not the case with PHT (invisible mouse pointer etc).

Best regards: dlanor

Ok, thanks for a good answer dlanor. Bummer to hear that native support for a mouse device is the problem, will try your keyboard solution.

Lets hope they implement support in the future. I still like Plex more than other solutions.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.