Home | Trees | Indices | Help |
---|
|
Process events objects, can be specialized via subclassing, thus its behavior can be overriden:
Note: you should not override __init__ in your subclass instead define a my_init() method, this method will be called automatically from the constructor of this class with its optionals parameters.
|
|||
|
|||
|
|||
bool |
|
||
|
|||
|
|||
|
|||
Inherited from Inherited from |
|
|||
pevent = None
|
|
|||
Inherited from |
|
Enable chaining of ProcessEvent instances.
|
This method is called from ProcessEvent.__init__(). This method is empty here and must be redefined to be useful. In effect, if you need to specifically initialize your subclass' instance then you just have to override this method in your subclass. Then all the keyworded arguments passed to ProcessEvent.__init__() will be transmitted as parameters to this method. Beware you MUST pass keyword arguments though.
|
To behave like a functor the object must be callable. This method is a dispatch method. Its lookup order is:
|
By default this method only reports warning messages, you can overredide it by subclassing ProcessEvent and implement your own process_IN_Q_OVERFLOW method. The actions you can take on receiving this event is either to update the variable max_queued_events in order to handle more simultaneous events or to modify your code in order to accomplish a better filtering diminishing the number of raised events. Because this method is defined, IN_Q_OVERFLOW will never get transmitted as arguments to process_default calls.
|
Default processing event method. By default does nothing. Subclass ProcessEvent and redefine this method in order to modify its behavior.
|
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Thu Jun 4 11:54:20 2015 | http://epydoc.sourceforge.net |