[vdr] Re: [ANNOUNCE] Remote Control Plugin 0.3.1

[Jeremy Hall <jhall@maoz.com>]

Hi,

yes I figured that out, and in fact with 1.3.7 I managed to get things 
going, however it won't display any of the text to the remote plugin, 
although it will accept keys from it, so I can, for example, press 
appropriate keys and the rotor plugin is doing something, but since it 
makes its own OSD interface, the remote plugin does not seem to have 
access to this.

I guess the solution would be to try and rewrite some of the rotor plugin
to use the cStatus interface, avoiding its graphics and colours, but 
making the data usable to the user.

Given that I have an installer showing up tomorrow to put up a dish that i 
have waited over a year and a half to install, I'd like to solve this 
problem in some way by then.

_J

In the new year, Oliver Endriss wrote:
> On Sunday 23 May 2004 07:09, Jeremy Hall wrote:
> > I was using DEBUG_OSD in 1.2.x and 1.3.6 with the rotor plugin, but when I 
> > selected the rotor menu, it seg faulted, probably because it did not 
> > intend to support DEBUG_OSD.  I applied the 0.3.1a diff and ran vdr-1.3.7, 
> > however it still wants me to learn keys and that part won't display.  Does 
> > the new OSD have a similar hack that the old one did to learn keys?
> 
> AFAIK, key learning did not change in vdr 1.3.7: Key learning messages
> are not sent through the cStatus interface. :-(
> 
> As soon as there is a good solution, I will update the remote plugin.
> 
> Anyway, you have to do key learning only once. You can copy remote.conf
> from vdr 1.2.6/1.3.6 and use it with vdr 1.3.7. (But I don't know whether
> key learning can be done using DEBUG_OSD.)
> 
> CU
> Oliver
> 
> 
> -- 
> Info:
> To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.
> 



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.