[vdr] Re: cReceivers in plugins

[Jan Ekholm <chakie@infa.abo.fi>]

On Fri, 9 May 2003, Klaus Schmidinger wrote:

<schnipp schnapp>

>The clean way _is_ to implement a cStatus class and monitor the device(s)
>there.

That way seems to actually be very easy to implement and works a lot
better.

I'm reading the plugin guide and looking at the little example cReceiver
subclass there. It inherits cThread, which I find a bit weird. The data
received in Receive() should be buffered and given to some thread for
processing, but must a custom receiver also inherit cThread?

At least my receiver now manages to break the stream on the primary
device. :) Which is a bit weird, as it shouldn't even do anything unless
there is data on the PID it is interested in? At least looking at
cDevice::Action() the receiver shouldn't interfere in any way until it
gets data on its PID and Receive() gets called. Need to read up a bit more
on the VDR source.

-- 
  In the beginning the Universe was created. This has made a lot of people
   very angry and been widely regarded as a bad move. 
                                                        -- Douglas Adams





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