Welcome Guest Search | Active Topics | Sign In | Register

Wait for angular to render content before executing eoapi.extInvoke Options
Canvas Tech
Posted: Tuesday, December 18, 2018 4:39:57 PM
Rank: Newbie
Groups: Member

Joined: 7/23/2018
Posts: 6
Hi.

I'm trying to use eoapi.extInvoke once content is rendered and communicate back to the api in c#. I'm wondering if there is a way I can wait for angular to complete rendering the UI before eoapi.extInvoke is executed. It doesn't seem to be working unless I add my invoke call outside angular domain.

The idea behind this is, once angular completed rendering the web page, invoke function will send the html code generated so that I can store in on the backend. I'm currently using EO.PDF to convert html to PDF but I need to also save the generated html now. I figured this invoke javascript feature would be useful but it's executing before expected.


eo_support
Posted: Tuesday, December 18, 2018 5:49:37 PM
Rank: Administration
Groups: Administration

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

There is nothing preventing you from doing that ---- but when angular has completed rendering the UI is completely a matter to angular --- the browser engine would have no knowledge to it. So you will need to look into angular's documentation to see if you can find any way to do that.

Thanks!
Canvas Tech
Posted: Wednesday, December 19, 2018 8:55:14 AM
Rank: Newbie
Groups: Member

Joined: 7/23/2018
Posts: 6
Hi,

Thanks for the reply. Yes we are aware of angular side to notify when page is fully rendered, but the extInvoke method is not called inside angular logic. I figure it only recognized pure javascript? Angular side is ready to notify, but when we try to execute eoapi.extInvoke at that time, nothing happens.

Does it only recognize javascript when using the webView?
eo_support
Posted: Wednesday, December 19, 2018 9:13:51 AM
Rank: Administration
Groups: Administration

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

I am not sure what you meant by "pure JavaScript". extInvoke is pure JavaScript ---- it's just it only exists when the page runs inside EO.WebBrowser. It's provided by our product so it does not exist anywhere else. As such if you try to load a page that calls extInvoke in Google Chrome browser, you will get an error.

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.