[vdr] Concerns about changing the API-definition of 'cStatus::Replaying()' and 'cStatus::Recording()' of VDR?

Jeremy Hall jhall at maoz.com
Mon Dec 19 14:47:23 CET 2005


In the new year, Oliver Endriss wrote:
> Klaus Schmidinger wrote:
> 
> Imho it is far more dangerous to break a plugin at run-time because
> changes are not obvious. Incompatible changes of an interface should
> always break compilation. I have no problems to release a new version
> of the remote plugin...
> 
> Recording/Replaying should pass the _same_ file name (short name, full
> name or whatever).
> 
> If a recording has been stopped, Recording() should also pass the file
> name. Otherwise you never know which recording has stopped. ;-(
> 
> For example:
>   void Recording(const cDevice *Device, const char *FileName, bool On)
> 
> The same should be done for Replaying().
>   void Replaying(const cControl *Control, const char *FileName, bool On)
> 
> Just my 2 cents.
> 
What about an object-oriented approach, where the recording knows whether 
it is playing or not and on which device.  What about attaching signals to 
the callbacks and when the recording is stopped, a signal can be emitted.

_J

> Oliver
> 
> -- 
> --------------------------------------------------------
> VDR Remote Plugin available at
> http://www.escape-edv.de/endriss/vdr/
> --------------------------------------------------------
> 
> _______________________________________________
> vdr mailing list
> vdr at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 




More information about the vdr mailing list