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
Implement external message pump, still experimental (cztomczak#246).
Add new option ApplicationSettings.external_message_pump. This is
experimental, actually it makes app slower, reported issue in upstream.
Add cefpython.GetAppSetting() func.
Show CEF Python version in unit test runner.
Downloads are handled automatically. A default `SaveAs` file dialog provided by OS is displayed. See also the [DownloadHandler](DownloadHandler.md) wiki page.
149
150
150
151
152
+
### external_message_pump
153
+
154
+
(bool)
155
+
Default: False
156
+
157
+
EXPERIMENTAL: currently this option makes browser slower, so don't use it.
158
+
Reported issue in upstream, see Issue #246 for details.
159
+
160
+
It is recommended to use this option as a replacement for calls to
161
+
cefpython.MessageLoopWork(). CEF Python will do these calls automatically
162
+
using CEF's OnScheduleMessagePumpWork. This results in improved performance
163
+
and resolves some bugs. See Issue #246 for more details.
164
+
165
+
Description from upstream CEF:
166
+
> Set to true (1) to control browser process main (UI) thread message pump
167
+
> scheduling via the CefBrowserProcessHandler::OnScheduleMessagePumpWork()
168
+
> callback. This option is recommended for use in combination with the
169
+
> CefDoMessageLoopWork() function in cases where the CEF message loop must be
170
+
> integrated into an existing application message loop (see additional
171
+
> comments and warnings on CefDoMessageLoopWork). Enabling this option is not
172
+
> recommended for most users; leave this option disabled and use either the
173
+
> CefRunMessageLoop() function or multi_threaded_message_loop if possible.
This function should be called on the main application thread (UI thread) to initialize CEF when the application is started. A call to Initialize() must have a corresponding call to Shutdown() so that CEF exits cleanly. Otherwise when application closes data (eg. storage, cookies) might not be saved to disk or the process might freeze (experienced on Windows XP).
@@ -186,8 +187,14 @@ List of threads in the Renderer process:
186
187
|__Return__| void |
187
188
188
189
Run the CEF message loop. Use this function instead of an application-
189
-
provided message loop to get the best balance between performance and CPU usage. This function should only be called on the main application thread (UI thread) and only if cefpython.Initialize() is called with a
190
-
[ApplicationSettings](ApplicationSettings.md).multi_threaded_message_loop value of false. This function will block until a quit message is received by the system.
190
+
provided message loop to get the best balance between performance and
191
+
CPU usage. This function should only be called on the main application
192
+
thread (UI thread) and only if cefpython.Initialize() is called with a
0 commit comments