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 from the constructor of this class with its optional parameters.
|
|||
|
|||
|
|||
bool |
|
||
|
|||
|
|||
|
|||
Inherited from Inherited from |
|
|||
pevent = None
|
|
|||
Inherited from |
|
Enable chaining of ProcessEvent instances.
|
This method is called from base constructor ProcessEvent.__init__(). This method is useless here and is meant to be redifined in a subclass of ProcessEvent. In effect, when subclassing just override this method if you want to provide custom initialization to your subclass' instance. 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 Mon Nov 2 22:06:42 2009 | http://epydoc.sourceforge.net |