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

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Jeremy Hall wrote:
> 
> right, but when the rotor plugin calls OpenRaw() it gets 0 back because of
> DEBUG_OSD and when it tries to run osd->create() it crashes

DEBUG_OSD mode is a pure *text* mode, so there can be no "raw OSD".

If the rotor plugin requires graphics, then it can't be used with DEBUG_OSD.
I don't know what the rotor plugin displays, but I would expect that it should
be possible to use the features provided by cSkinDisplayMenu for this, and these
will be mapped to an upcoming 'curses' skin.

Klaus

> _J
> 
> In the new year, Klaus Schmidinger wrote:
> > Thomas Bergwinkl wrote:
> > >
> > > > > 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.
> >
> > Don't panic - there will be a 'curses' skin plugin that implements the
> > functionality of the old DEBUG_OSD feature.
> >
> > If you absolutely need the textual OSD, just stay with VDR 1.3.6 until then.
> >
> > Klaus


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