You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: api/cefpython.md
+21-5Lines changed: 21 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,11 +154,27 @@ provided message loop to get the best balance between performance and CPU usage.
154
154
| --- | --- |
155
155
|__Return__| void |
156
156
157
-
Perform a single iteration of CEF message loop processing. This function is used to integrate the CEF message loop into an existing application message loop. Care must be taken to balance performance against excessive CPU usage. This function should only be called on the main application thread (UI thread) and only if cefpython.Initialize() is called with a [ApplicationSettings](ApplicationSettings.md).multi_threaded_message_loop value of false. This function will not block.
158
-
159
-
Alternatively you could create a periodic timer (with 10 ms interval) that calls cefpython.MessageLoopWork().
160
-
161
-
MessageLoopWork() is not tested on OS X and there are known issues - according to [this post](http://www.magpcss.org/ceforum/viewtopic.php?p=27124#p27124) by Marshall.
157
+
Description from upstream CEF:
158
+
159
+
> Perform a single iteration of CEF message loop processing. This function is
160
+
> provided for cases where the CEF message loop must be integrated into an
161
+
> existing application message loop. Use of this function is not recommended
162
+
> for most users; use either the CefRunMessageLoop() function or
163
+
> CefSettings.multi_threaded_message_loop if possible. When using this function
164
+
> care must be taken to balance performance against excessive CPU usage. It is
165
+
> recommended to enable the CefSettings.external_message_pump option when using
166
+
> this function so that CefBrowserProcessHandler::OnScheduleMessagePumpWork()
167
+
> callbacks can facilitate the scheduling process. This function should only be
168
+
> called on the main application thread and only if CefInitialize() is called
169
+
> with a CefSettings.multi_threaded_message_loop value of false. This function
170
+
> will not block.
171
+
172
+
Alternatively you could create a periodic timer (with 10 ms interval) that calls
173
+
cefpython.MessageLoopWork().
174
+
175
+
MessageLoopWork() is not tested on OS X and there are known issues - according to
176
+
[this post](http://www.magpcss.org/ceforum/viewtopic.php?p=27124#p27124) by
0 commit comments