DBus interface for monitoring the Zeitgeist log for certain types of events. When using the Python bindings monitors are normally instantiated indirectly by calling ZeitgeistClient.install_monitor
It is important to understand that the Monitor instance lives on the client side, and expose a DBus service there, and the Zeitgeist engine calls back to the monitor when matching events are registered.
Namespace: Zeitgeist.Datamodel
Assembly: zeitgeist-sharp (in zeitgeist-sharp.dll)
Assembly Versions: 0.8.0.0
See Also: Inherited members from object.
⊟ Public Constructors
⊟ Public Events
⊟ Monitor Constructor
Create a new instance of Monitor which can be used for notifying the client that some event has been inserted or deleted which matches the event template
public Monitor (string monitorPath)⊟ Parameters
- monitorPath
- The DBus path over which the bus is activated string
⊟ Remarks
Documentation for this section has not yet been entered.⊟ Requirements
Namespace: Zeitgeist.Datamodel
Assembly: zeitgeist-sharp (in zeitgeist-sharp.dll)
Assembly Versions: 0.8.0.0
⊟ Deleted Event
The event which is fired in the case of an event is deleted which matches the Event Templates
public event NotifyDeleteHandler Deleted⊟ Remarks
Documentation for this section has not yet been entered.⊟ Requirements
Namespace: Zeitgeist.Datamodel
Assembly: zeitgeist-sharp (in zeitgeist-sharp.dll)
Assembly Versions: 0.8.0.0
⊟ Inserted Event
The event which is fired in the case of an event is inserted which matches the Event Templates
public event NotifyInsertHandler Inserted⊟ Remarks
Documentation for this section has not yet been entered.⊟ Requirements
Namespace: Zeitgeist.Datamodel
Assembly: zeitgeist-sharp (in zeitgeist-sharp.dll)
Assembly Versions: 0.8.0.0