hello ,
we are using winccoa 3.16 P001 and we use the BIRT as a third party tool to view a specific report in a web view wed-jet .
the attached snapshot shows the error that keeps coming when we press the print button to print the report as a PDF or DOCS or XL ,knowing that if we take the link written in the picture and put it directly in Microsoft explorer it will work fine .
if the snapshot didn't attached please find the following wrote in the snapshoty :
"Frame load interrupted by policy change"
"Failed to load URL http://10.218.28.11:8080/WebViewerExamp ... rite=false.
WebKit Error 102"
can you please tell us how to fix this issue or what is the reason ?
Winccoa birt report issue
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Winccoa birt report issue
I had a look at the description but I do not understand which components you are using.
Which tool displays the error shown in the screenshot?
What is a "web view wed-jet"?
Do you mean a QT webview widget?
Best Regards
Leopold Knipp
Senior Support Specialist
Which tool displays the error shown in the screenshot?
What is a "web view wed-jet"?
Do you mean a QT webview widget?
Best Regards
Leopold Knipp
Senior Support Specialist
- hussamshaar
- Posts:2
- Joined: Mon Aug 06, 2018 11:13 am
Re: Winccoa birt report issue
yes, we use QT web view widget.
we use the QT web view widget to show birt report inside win cc panel, but when we try to export the report give us an error.
and there is no error when we trying from google chrome or another browser
we use the QT web view widget to show birt report inside win cc panel, but when we try to export the report give us an error.
and there is no error when we trying from google chrome or another browser
- Andorhal
- Posts:127
- Joined: Wed Nov 12, 2014 8:04 am
Re: Winccoa birt report issue
This is an issue with the underlaying Webkit (the browser engine within the WebView EWO).
We are changing the the engine to WebEngine (Chromium based) in the future.
Until then the only solution is to use a standard browser.
We are changing the the engine to WebEngine (Chromium based) in the future.
Until then the only solution is to use a standard browser.