Welcome Guest Search | Active Topics | Sign In | Register

Best Practice: Initialize EO.Webbrowser for smooth Startup Options
xpecto AG
Posted: Friday, March 13, 2015 4:54:08 PM
Rank: Newbie
Groups: Member

Joined: 3/13/2015
Posts: 2
Hi,
our Application takes approx 10 secs to start.
the EO.Webbrowser adds 2-3 secs to this, but this shouldn't be necessary.

The heaving lifting occurs when the control is shown and thus blocks the UI-thread.
Is it possible to initialize a part or issue a call at an early stage to reduce waiting?

e.g. creating a webview right at startup for later use? (second thread)
or is there a call to initialize the whole system upfront?



eo_support
Posted: Friday, March 13, 2015 6:24:29 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

Yes. You can create a WebView right at startup. However make sure you create it with the ThreadRunner object:

http://www.essentialobjects.com/doc/6/eo.webbrowser.threadrunner.createwebview_overloads.aspx

The reason is because the WebView needs a message loop in order to initialize correctly and a "regular" worker thread doesn't have that. ThreadRunner maintain an internal thread that runs a message loop and create the WebView in that thread.

Another option you can try is the multi-DLL build. See here for more details:

http://www.essentialobjects.com/doc/6/install/multi_dll_build.aspx

You can use both options at the same time.

Hope this helps. Please feel free to let us know if you have any more questions.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.