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

[Thomas.Bergwinkl@t-online.de (Thomas Bergwinkl)]

> > 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.
>
> True. That's why the remote plugin cannot provide a real osd.
>
> > 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.
> >

Yes, the plugin draws the OSD itself. Now I'm wondering how to support
debug_osd. Would it be enough, if I simply add some
cStatus::OsdTextItem() calls, which tells the user what function ('Drive
East','Drive West', ...) is selected. But then the user isn't informed
about all available options and how to reach them. (There are 3 columns
and 7 rows on the screen, so you have to press for example 1xRight and
2xDown) I have never worked with the debug_osd, so I don't know how it
is solved in other menues. After some recordings will be finished on my
vdr, I will have a look.


Thomas



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