summaryrefslogtreecommitdiff
path: root/PLUGINS.html
diff options
context:
space:
mode:
Diffstat (limited to 'PLUGINS.html')
-rw-r--r--PLUGINS.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/PLUGINS.html b/PLUGINS.html
index a0f7ebc9..a3adc937 100644
--- a/PLUGINS.html
+++ b/PLUGINS.html
@@ -857,12 +857,12 @@ plugin's name, and <tt>0.0.1</tt> will be your plugin's current version number.
<center><i><b>A piece of the action</b></i></center><p>
If a plugin wants to get informed on various events in VDR, it can derive a class from
-<tt>cStatusMonitor</tt>, as in
+<tt>cStatus</tt>, as in
<p><table><tr><td bgcolor=#F0F0F0><pre><br>
#include &lt;vdr/status.h&gt;
-class cMyStatusMonitor : public cStatusMonitor {
+class cMyStatusMonitor : public cStatus {
protected:
virtual void ChannelSwitch(const cDevice *Device, int ChannelNumber);
};
@@ -914,15 +914,15 @@ Note that the actual object is created in the <tt>Start()</tt> function, not in
constructor! It is also important to delete the object in the destructor, in order to
avoid memory leaks.
<p>
-A Plugin can implement any number of <tt>cStatusMonitor</tt> derived objects, and once
+A Plugin can implement any number of <tt>cStatus</tt> derived objects, and once
the plugin has been started it may create and delete them as necessary.
-No further action apart from creating an object derived from <tt>cStatusMonitor</tt>
+No further action apart from creating an object derived from <tt>cStatus</tt>
is necessary. VDR will automatically hook it into a list of status monitors, with
their individual virtual member functions being called in the same sequence as the
objects were created.
<p>
See the file <tt>status.h</tt> for detailed information on which status monitor
-member functions are available in <tt>cStatusMonitor</tt>. You only need to implement
+member functions are available in <tt>cStatus</tt>. You only need to implement
the functions you actually want to use.
<!--X1.1.3--></td></tr></table>