LinuxMCE Forums

General => Developers => Topic started by: zaphodB on April 21, 2008, 05:11:53 PM

Title: VDR with Gyration Gyromouse
Post by: zaphodB on April 21, 2008, 05:11:53 PM
Hi,

at time it's impossible to handle the vdr and his buttons fully in lmce only with the Gyration Gyromouse.

Would it be possible in the future, to handle vdr full with this mouse or do I have to buy a Fiire remote.

I've buyed all my equipment in 11.2007 after watching the video an read the wiki.

regards

Thorsten

Title: Re: VDR with Gyration Gyromouse
Post by: mami on May 08, 2008, 05:21:23 PM
I have a Fiire remote and use VDR.
I don't work as i want it to do, so i'm trying to find out where to change whitch key does what.

Any one know?
Like Red, Green, Yellow, Blue buttons on the remote. How to get them working in VDR?

/Mami
Title: Re: VDR with Gyration Gyromouse
Post by: totallymaxed on May 11, 2008, 01:25:17 AM
Quote from: mami on May 08, 2008, 05:21:23 PM
I have a Fiire remote and use VDR.
I don't work as i want it to do, so i'm trying to find out where to change whitch key does what.

Any one know?
Like Red, Green, Yellow, Blue buttons on the remote. How to get them working in VDR?

/Mami

There will be an update for LinuxMCE-0710 to support the colour buttons shortly.

Andrew
Title: Re: VDR with Gyration Gyromouse
Post by: mami on May 11, 2008, 09:37:03 AM
Sounds good. But is there any way to change key if I want, or is all keys hardcoded?

Edit:
I answer my own question: It's hardcoded in src/Orbiter/Linux/HID*.cpp/h (only gyro keys!)

/Mami
Title: Re: VDR with Gyration Gyromouse
Post by: nite_man on July 10, 2008, 11:16:17 AM
I'm also interested to use Gyration or some other RF remote with VDR. Is there some manual howto configure it?
Title: Re: VDR with Gyration Gyromouse
Post by: totallymaxed on July 13, 2008, 04:24:14 PM
Quote from: mami on May 11, 2008, 09:37:03 AM
Sounds good. But is there any way to change key if I want, or is all keys hardcoded?

Edit:
I answer my own question: It's hardcoded in src/Orbiter/Linux/HID*.cpp/h (only gyro keys!)

/Mami

The other problem with A gyro mouse currently is that while there are 'bits' of the standard vdr OSD still being used (as there are currently... and will be for the foreseeable future) there is a problem in that they do not support mouse based interaction at all. So in that sense they are really not suitable for purely mouse based controls. The Fiire remote an the MCE Gyration remote are better from that perspective as you have a full set of 'normal' remote buttons.

Andrew
Title: Re: VDR with Gyration Gyromouse
Post by: tschak909 on July 14, 2008, 02:10:56 AM
why not overlay transparent designobjs with tab stop enabled, and trigger commands on that? ;-)

-Thom
Title: Re: VDR with Gyration Gyromouse
Post by: colinjones on July 14, 2008, 02:35:27 AM
Andrew

Does that mean that the "colour" buttons on the Fiire remotes will be taken over whilst in VDR OSD menus? Currently they act to shortcut to Video/Audio/etc media grids.

Would be nice if their function was taken over when you go into the VDR menus and returned when you come out...
Title: Re: VDR with Gyration Gyromouse
Post by: totallymaxed on July 18, 2008, 11:43:36 PM
Quote from: colinjones on July 14, 2008, 02:35:27 AM
Andrew

Does that mean that the "colour" buttons on the Fiire remotes will be taken over whilst in VDR OSD menus? Currently they act to shortcut to Video/Audio/etc media grids.

Would be nice if their function was taken over when you go into the VDR menus and returned when you come out...

Yep thats the plan ;-)
Title: Re: VDR with Gyration Gyromouse
Post by: totallymaxed on July 18, 2008, 11:48:38 PM
Quote from: tschak909 on July 14, 2008, 02:10:56 AM
why not overlay transparent designobjs with tab stop enabled, and trigger commands on that? ;-)

-Thom


Hmmmm... sounds like a complex task as the transparent design objects would have to dynamically change function (and in many cases position) as the vdr OSD updated and changed state and/or changed menu screen. I cant see how those state changes could be dynamically fed back to the transparent design objects on the fly as the user interacted with the OSD?

Andrew