1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
|
.. wxPython Phoenix documentation
This file was generated by Phoenix's sphinx generator and associated
tools, do not edit by hand.
Copyright: (c) 2011-2018 by Total Control Software
License: wxWindows License
.. include:: headings.inc
.. _wx.IdleEvent:
==========================================================================================================================================
|phoenix_title| **wx.IdleEvent**
==========================================================================================================================================
This class is used for idle events, which are generated when the system becomes idle.
Note that, unless you do something specifically, the idle events are not sent if the system remains idle once it has become it, e.g. only a single idle event will be generated until something else resulting in more normal events happens and only then is the next idle event sent again.
If you need to ensure a continuous stream of idle events, you can either use :meth:`wx.IdleEvent.RequestMore` method in your handler or call :ref:`wx.WakeUpIdle` periodically (for example from a timer event handler), but note that both of these approaches (and especially the first one) increase the system load and so should be avoided if possible.
By default, idle events are sent to all windows, including even the hidden ones because they may be shown if some condition is met from their ``wxEVT_IDLE`` (or related ``wxEVT_UPDATE_UI`` ) handler. The children of hidden windows do not receive idle events however as they can't change their state in any way noticeable by the user. Finally, the global :ref:`wx.App` object also receives these events, as usual, so it can be used for any global idle time processing.
If sending idle events to all windows is causing a significant overhead in your application, you can call :meth:`wx.IdleEvent.SetMode` with the value ``wx.IDLE_PROCESS_SPECIFIED``, and set the ``wx.WS_EX_PROCESS_IDLE`` extra window style for every window which should receive idle events, all the other ones will not receive them in this case.
.. _IdleEvent-events:
|events| Events Emitted by this Class
=====================================
Handlers bound for the following event types will receive a :ref:`wx.IdleEvent` parameter.
Event macros:
- EVT_IDLE: Process a ``wxEVT_IDLE`` event.
|phoenix_title| Delayed Action Mechanism
========================================
:ref:`wx.IdleEvent` can be used to perform some action "at slightly later time". This can be necessary in several circumstances when, for whatever reason, something can't be done in the current event handler. For example, if a mouse event handler is called with the mouse button pressed, the mouse can be currently captured and some operations with it ``wxEVT_IDLE`` handler when it is called the next time instead of doing it immediately. This can be achieved in two different ways: when using static event tables, you will need a flag indicating to the (always connected) idle event handler whether the desired action should be performed. The originally called handler would then set it to indicate that it should indeed be done and the idle handler itself would reset it to prevent it from doing the same action again. Using dynamically connected event handlers things are even simpler as the original event handler can simply :meth:`wx.EvtHandler.Connect` or :meth:`wx.EvtHandler.Bind` the idle event handler which would only be executed then and could :meth:`wx.EvtHandler.Disconnect` or :meth:`wx.EvtHandler.Unbind` itself.
.. seealso:: :ref:`Events and Event Handling <events and event handling>`, :ref:`wx.UpdateUIEvent`, :meth:`wx.Window.OnInternalIdle`
|
|class_hierarchy| Class Hierarchy
=================================
.. raw:: html
<div id="toggleBlock" onclick="return toggleVisibility(this)" class="closed" style="cursor:pointer;">
<img id="toggleBlock-trigger" src="_static/images/closed.png"/>
Inheritance diagram for class <strong>IdleEvent</strong>:
</div>
<div id="toggleBlock-summary" style="display:block;"></div>
<div id="toggleBlock-content" style="display:none;">
<p class="graphviz">
<center><img src="_static/images/inheritance/wx.IdleEvent_inheritance.png" alt="Inheritance diagram of IdleEvent" usemap="#dummy" class="inheritance"/></center>
</div>
<script type="text/javascript">toggleVisibilityOnLoad(document.getElementById('toggleBlock'))</script>
<map id="dummy" name="dummy"> <area shape="rect" id="node1" href="wx.Event.html" title="wx.Event" alt="" coords="15,83,93,112"/> <area shape="rect" id="node3" href="wx.IdleEvent.html" title="wx.IdleEvent" alt="" coords="5,160,104,189"/> <area shape="rect" id="node2" href="wx.Object.html" title="wx.Object" alt="" coords="13,5,95,35"/> </map>
</p>
|
|method_summary| Methods Summary
================================
================================================================================ ================================================================================
:meth:`~wx.IdleEvent.__init__` Constructor.
:meth:`~wx.IdleEvent.GetMode` Static function returning a value specifying how wxWidgets will send idle events: to all windows, or only to those which specify that they will process the events.
:meth:`~wx.IdleEvent.MoreRequested` Returns ``True`` if the OnIdle function processing this event requested more processing time.
:meth:`~wx.IdleEvent.RequestMore` Tells wxWidgets that more processing is required.
:meth:`~wx.IdleEvent.SetMode` Static function for specifying how wxWidgets will send idle events: to all windows, or only to those which specify that they will process the events.
================================================================================ ================================================================================
|
|api| Class API
===============
.. class:: wx.IdleEvent(Event)
**Possible constructors**::
IdleEvent()
This class is used for idle events, which are generated when the
system becomes idle.
.. method:: __init__(self)
Constructor.
.. staticmethod:: GetMode()
Static function returning a value specifying how wxWidgets will send idle events: to all windows, or only to those which specify that they will process the events.
:rtype: :ref:`wx.IdleMode`
.. seealso:: :meth:`SetMode` .
.. method:: MoreRequested(self)
Returns ``True`` if the OnIdle function processing this event requested more processing time.
:rtype: `bool`
.. seealso:: :meth:`RequestMore`
.. method:: RequestMore(self, needMore=True)
Tells wxWidgets that more processing is required.
This function can be called by an OnIdle handler for a window or window event handler to indicate that `App.OnIdle` should forward the OnIdle event once more to the application windows.
If no window calls this function during OnIdle, then the application will remain in a passive event loop (not calling OnIdle) until a new event is posted to the application by the windowing system.
:param `needMore`:
:type `needMore`: bool
.. seealso:: :meth:`MoreRequested`
.. staticmethod:: SetMode(mode)
Static function for specifying how wxWidgets will send idle events: to all windows, or only to those which specify that they will process the events.
:param `mode`: Can be one of the :ref:`wx.IdleMode` values. The default is ``wx.IDLE_PROCESS_ALL``.
:type `mode`: wx.IdleMode
|
