mirror of
https://bitbucket.org/chromiumembedded/cef
synced 2025-06-05 21:39:12 +02:00
libcef:
- Allow execution of CEF using the current application's message loop. tests/cefclient: - Support running of the cefclient application using a single message loop via the TEST_SINGLE_THREADED_MESSAGE_LOOP define. Issue #1, Suggested implementation by: vridosh git-svn-id: https://chromiumembedded.googlecode.com/svn/trunk@13 5089003a-bbd8-11dd-ad1f-f1f9622dbc98
This commit is contained in:
@@ -39,14 +39,21 @@
|
||||
|
||||
// This function should only be called once when the application is started.
|
||||
// Create the thread to host the UI message loop. A return value of true
|
||||
// indicates that it succeeded and false indicates that it failed.
|
||||
bool CefInitialize();
|
||||
// indicates that it succeeded and false indicates that it failed. Set
|
||||
// |multi_threaded_message_loop| to true to have the message loop run in
|
||||
// a separate thread. If |multi_threaded_message_loop| is false than
|
||||
// the CefDoMessageLoopWork() function must be called from your message loop.
|
||||
bool CefInitialize(bool multi_threaded_message_loop);
|
||||
|
||||
// This function should only be called once before the application exits.
|
||||
// Shut down the thread hosting the UI message loop and destroy any created
|
||||
// windows.
|
||||
void CefShutdown();
|
||||
|
||||
// Perform message loop processing. Has no affect if the browser UI loop is
|
||||
// running in a separate thread.
|
||||
void CefDoMessageLoopWork();
|
||||
|
||||
|
||||
// Interface defining the the reference count implementation methods. All
|
||||
// framework classes must implement the CefBase class.
|
||||
|
Reference in New Issue
Block a user