+ """
+ IdleEvent_CanSend(Window win) -> bool
+
+ Returns ``True`` if it is appropriate to send idle events to this
+ window.
+
+ This function looks at the mode used (see `wx.IdleEvent.SetMode`), and
+ the wx.WS_EX_PROCESS_IDLE style in window to determine whether idle
+ events should be sent to this window now. By default this will always
+ return ``True`` because the update mode is initially
+ wx.IDLE_PROCESS_ALL. You can change the mode to only send idle events
+ to windows with the wx.WS_EX_PROCESS_IDLE extra window style set.
+ """
+ return _core_.IdleEvent_CanSend(*args, **kwargs)
+
+#---------------------------------------------------------------------------
+
+class ClipboardTextEvent(CommandEvent):
+ """
+ A Clipboard Text event is sent when a window intercepts a text
+ copy/cut/paste message, i.e. the user has cut/copied/pasted data
+ from/into a text control via ctrl-C/X/V, ctrl/shift-del/insert, a
+ popup menu command, etc. NOTE : under windows these events are *NOT*
+ generated automatically for a Rich Edit text control.
+ """
+ thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
+ __repr__ = _swig_repr
+ def __init__(self, *args, **kwargs):
+ """
+ __init__(self, EventType type=wxEVT_NULL, int winid=0) -> ClipboardTextEvent
+
+ A Clipboard Text event is sent when a window intercepts a text
+ copy/cut/paste message, i.e. the user has cut/copied/pasted data
+ from/into a text control via ctrl-C/X/V, ctrl/shift-del/insert, a
+ popup menu command, etc. NOTE : under windows these events are *NOT*
+ generated automatically for a Rich Edit text control.
+ """
+ _core_.ClipboardTextEvent_swiginit(self,_core_.new_ClipboardTextEvent(*args, **kwargs))
+_core_.ClipboardTextEvent_swigregister(ClipboardTextEvent)
+
+#---------------------------------------------------------------------------
+
+class PyEvent(Event):
+ """
+ wx.PyEvent can be used as a base class for implementing custom event
+ types in Python. You should derived from this class instead of
+ `wx.Event` because this class is Python-aware and is able to transport
+ its Python bits safely through the wxWidgets event system and have
+ them still be there when the event handler is invoked.
+
+ :see: `wx.PyCommandEvent`
+
+ """
+ thisown = property(lambda x: x.this.own(), lambda x, v: x.this.own(v), doc='The membership flag')
+ __repr__ = _swig_repr
+ def __init__(self, *args, **kwargs):
+ """__init__(self, int winid=0, EventType eventType=wxEVT_NULL) -> PyEvent"""
+ _core_.PyEvent_swiginit(self,_core_.new_PyEvent(*args, **kwargs))
+ self._SetSelf(self)
+
+ __swig_destroy__ = _core_.delete_PyEvent
+ __del__ = lambda self : None;
+ def _SetSelf(*args, **kwargs):
+ """_SetSelf(self, PyObject self)"""
+ return _core_.PyEvent__SetSelf(*args, **kwargs)
+
+ def _GetSelf(*args, **kwargs):
+ """_GetSelf(self) -> PyObject"""
+ return _core_.PyEvent__GetSelf(*args, **kwargs)
+
+_core_.PyEvent_swigregister(PyEvent)
+
+class PyCommandEvent(CommandEvent):
+ """
+ wx.PyCommandEvent can be used as a base class for implementing custom
+ event types in Python, where the event shoudl travel up to parent
+ windows looking for a handler. You should derived from this class
+ instead of `wx.CommandEvent` because this class is Python-aware and is
+ able to transport its Python bits safely through the wxWidgets event
+ system and have them still be there when the event handler is invoked.
projects / wxWidgets.git / blobdiff