CreateBrowserSync problem

[emerick]

I'm working on upgrading my WTL application from CEF1 to CEF3. Things are going great so far, but I've noticed that before my call to CreateBrowserSync returns, my application's OnIdle handler is firing. I realize that WTL is outside the scope of CEF, but would this be expected behavior? I'm concerned because I don't recall this happening when using CEF1.

I'm assuming that I will need to keep some kind of Boolean flag around to indicate when CreateBrowserSync has finished running, so that my OnIdle handler doesn't get confused (because it's currently trying to perform some browser-related actions)? If anyone has any tips on this, I'd love to hear them.

Emerick

[magreenblatt]

Are you using multi-threaded message loop mode in CEF? You might want to wait for the OnAfterCreated callback before trying to manipulate the browser.

[emerick]

Are you using multi-threaded message loop mode in CEF?

No, I have multi_threaded_message_loop set to false. Is this behavior expected in that case?

You might want to wait for the OnAfterCreated callback before trying to manipulate the browser.

Right, that makes sense. I'm not sure how I got away without doing this when using CEF1, but this clearly seems like the correct approach.

[magreenblatt]

Are you using multi-threaded message loop mode in CEF?

No, I have multi_threaded_message_loop set to false. Is this behavior expected in that case?

What thread is OnIdle running on? It seems strange that it would execute during the execution of CreateBrowserSync if they're running on the same thread.

[emerick]

It's running on the main UI thread (CrBrowserMain?) I agree that it seems like it shouldn't be happening. I'm going to double-check the flow for browser creation in my app; I'm starting to suspect that I'm just doing something wrong here...

[emerick]

This turned out to be a programming error in my application. Sorry for the false alarm and thanks for the help!