From bc06fc2ce38392605ef094cfe544faafad9c1cb8 Mon Sep 17 00:00:00 2001 From: Klaus Schmidinger Date: Fri, 9 Mar 2012 09:25:18 +0100 Subject: [PATCH] Changed displaying modified sections --- PLUGINS.html | 33 +++++++++++++++------------------ 1 file changed, 15 insertions(+), 18 deletions(-) diff --git a/PLUGINS.html b/PLUGINS.html index 5f936e56..4d939430 100644 --- a/PLUGINS.html +++ b/PLUGINS.html @@ -21,6 +21,9 @@ html, body { .modified { background-color: #FFDDDD; } +modified { + background-color: #FFDDDD; +} @@ -34,9 +37,9 @@ Copyright © 2009 Klaus Schmidinger
kls@tvdr.de
www.tvdr.de -
-Important modifications introduced since version 1.6 are marked like this. -
+
+Important modifications introduced since version 1.6 are marked like this. +

VDR provides an easy to use plugin interface that allows additional functionality to be added to the program by implementing a dynamically loadable library file. @@ -1221,10 +1224,10 @@ If a plugin wants to get informed on various events in VDR, it can derive a clas class cMyStatusMonitor : public cStatus { protected: - virtual void ChannelSwitch(const cDevice *Device, int ChannelNumber

, bool LiveView
); + virtual void ChannelSwitch(const cDevice *Device, int ChannelNumber, bool LiveView); }; -void cMyStatusMonitor::ChannelSwitch(const cDevice *Device, int ChannelNumber
, bool LiveView
) +void cMyStatusMonitor::ChannelSwitch(const cDevice *Device, int ChannelNumber, bool LiveView) { if (ChannelNumber) dsyslog("channel switched to %d on DVB %d", ChannelNumber, Device->CardIndex()); @@ -1510,9 +1513,7 @@ The above example sets up a receiver that wants to receive data from only one PID (for example the Teletext PID). In order to not interfere with other recording operations, it sets its priority to -1 (any negative value will allow a cReceiver to be detached from its cDevice at any time -
-in favor of a timer recording or live viewing). -
+in favor of a timer recording or live viewing).

Once a cReceiver has been created, it needs to be attached to a cDevice: @@ -1528,9 +1529,9 @@ the receiver is attached to the device that actually receives the current live video stream (this may be different from the primary device in case of Transfer Mode).

-

+ The cReceiver must be detached from its device before it is deleted. -
+

Filters

@@ -1808,9 +1809,7 @@ If the new device can receive, it most likely needs to provide a way of selecting which channel it shall tune to: 

-

-virtual int NumProvidedSystems(void) const;
-

+virtual int NumProvidedSystems(void) const;
 virtual bool ProvidesSource(int Source) const;
 virtual bool ProvidesTransponder(const cChannel *Channel) const;
 virtual bool ProvidesChannel(const cChannel *Channel, int Priority = -1, bool *NeedsDetachReceivers = NULL) const;
@@ -1859,9 +1858,7 @@ virtual bool HasDecoder(void) const;
 virtual bool CanReplay(void) const;
 virtual bool SetPlayMode(ePlayMode PlayMode);
 virtual int64_t GetSTC(void);
-

-virtual bool IsPlayingVideo(void) const;
-

+virtual bool IsPlayingVideo(void) const;
 virtual bool HasIBPTrickSpeed(void);
 virtual void TrickSpeed(int Speed);
 virtual void Clear(void);
@@ -1938,13 +1935,13 @@ void cMyDevice::MakePrimaryDevice(bool On)
 The OSD provider object is allocated on the heap and shall not be deleted
 (it will be deleted automatically in case a different device sets up an OSD
 provider, or when the program ends).
-
+

 Note that an OSD implementation need not be physically linked to the device
 in any way. All it needs to make sure is that the OSD will be visible to the
 user - whether this goes through OSD facilities of the physical device (like
 a "full featured" DVB card) or through a graphics adapter that overlays its
 output with the video signal, doesn't matter.
-
+

 

 In order to be able to determine the proper size of the OSD, the device
 should implement the function