Rank: Member Groups: Member
Joined: 8/8/2015 Posts: 12
|
Hi Support,
I'm experiencing a very strange issue with EO.WebBrowser WebViews.
My application opens up a form that displays web content. The form passes a class (also instantiated new with the form) that wraps a WebView a PictureBox Handle. This routine works flawlessly and web content is displayed as expected.
However, if I close the form (using Form.Close()), then instantiate a new instance of the same form (creating a new WebView and wrapper class), the web content flickers for a second, then stabilizes.
I wasn't too concerned with this until I began handling the NewWindow event. The first time I instantiate the form and cause the NewWindow event to trigger, the WebView will cause one new window to open. If I Close() the form and instantiate a new one, the NewWindow event will trigger TWO new windows. I have repeated this pattern up to three new windows.
It appears that the internal engine is still referencing WebViews that should be long gone after their forms are closed. I have tried to fix this issue by handling the FormClosing event and calling WebView.Close(), WebView.Destroy(), WebView.Dispose() and setting the WebView = null with no success.
Thanks.
|
Rank: Member Groups: Member
Joined: 8/8/2015 Posts: 12
|
This issue has been resolved.
The problem at hand had nothing to do with EO, and everything to do with not properly taking GUI elements out of scope.
Thank you anyway.
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,229
|
Glad to hear that you resolved the issue. Thank you very much for the update!
|