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
Some years ago, using VC++ code samples, we built an ActiveX based on WebView2 to browse web pages.
It’s been built vith VisualStudio 2019, for 32bit applications.
It is used as a graphic component on the screens of our product Movicon11.
Movicon11 is a SCADA application, built vith VisualStudio 2008 (32bit)
The ActiveX browser works good, once added to a screen.
When you have two ActiveX browser on the same screen, at the loading, an exception arises, code 0x8001010E (RPC_E_WRONG_THREAD).
Debugging, I can see an ActiveX that complete its initialization, the second generate the exception while calling CreateDispatcherQueueController.
The same thing happens when the ActiveX are on two different screens and I switch from one screen to the next.
When the ActivX are on different screens, if I spend sone second in a void screen, before to open the second screen, I do not see the exception. It seems like something needs some time to close, before initializing another ActiveX with success.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Some years ago, using VC++ code samples, we built an ActiveX based on WebView2 to browse web pages.
It’s been built vith VisualStudio 2019, for 32bit applications.
It is used as a graphic component on the screens of our product Movicon11.
Movicon11 is a SCADA application, built vith VisualStudio 2008 (32bit)
The ActiveX browser works good, once added to a screen.
When you have two ActiveX browser on the same screen, at the loading, an exception arises, code 0x8001010E (RPC_E_WRONG_THREAD).
Debugging, I can see an ActiveX that complete its initialization, the second generate the exception while calling CreateDispatcherQueueController.
The same thing happens when the ActiveX are on two different screens and I switch from one screen to the next.
When the ActivX are on different screens, if I spend sone second in a void screen, before to open the second screen, I do not see the exception. It seems like something needs some time to close, before initializing another ActiveX with success.
Beta Was this translation helpful? Give feedback.
All reactions