I just picked up Qt and QML for the first time and the first thing I wanted to get working was just to open Google Maps in a WebView but it doesn’t work.
Here’s the QML:
import QtQuick 2.0
import QtWebKit 3.0
Rectangle {
width: 1024
height: 960
WebView {
width: 1024
height: 960
anchors.centerIn: parent
url: "http://maps.google.com"
}
}
The window opens but the contents of the WebView are completely blank. If I try other websites then the correct web page is displayed.
What’s wrong with this code? I am not behind any proxy or firewall. I suspect it is something to do with HTTPS given that some maps APIs use HTTPS but I don’t see why HTTP would work but not HTTPS.
I am using Qt 5.1 on Windows 7 64-bit.
Related
I've just deployed the dialogflow messenger plugin via HTML to a second test website. In the first website, the chat window rendered perfectly. The second website however (a Magento PHP site that I don't have much control over) the same dialogflow with the same settings, shows all the responses from the bot as centered?
Here's the same chatbot, with the same HTML code, on a different (test) website running on my local machine (a flask site)
I've checked the available Dialogflow CX documentation - https://cloud.google.com/dialogflow/cx/docs/concept/integration/dialogflow-messenger - and I can't see any settings that would affect the alignment of text.
Agent html / CSS
Inline CSS:
<style>
df-messenger {
--df-messenger-button-titlebar-color: #ec008c;
}
</style>
Javascript:
HTML
<df-messenger
df-cx="true"
location="australia-southeast1"
chat-title="x"
agent-id="x"
chat-icon=xxxx/girl.png
language-code="en"
></df-messenger>
You need to compare all the Sources that the page uses in both websites and see it you are missing anything
(like this) :
If its the same then :
you have a non closed div that effects the chatting section .
you changed something in the functions that setts the plugin .
you are calling the same script multiple times so it appears on the
resources but doesn't cause errors in the console .
I have a link written in SwiftUI inside Widget View like this:
Link("Visit Apple",
destination: URL(string: "https://www.apple.com")!)
.font(.caption)
.foregroundColor(.red)
But now, I need to open this in Safari. Is it possible without opening the host app?
No, WidgetKit widgets always open their app. There’s no way around it. The best you can do is have your widget open your app (passing the web url) and then your app opens the passes URL in Safari automatically.
I have used adapter, authentication, server everything of MFP. But now I am stuck in Direct Update. If I am pushing mfpdev app webupdate direct update default dialog is coming and I can update application.
But issue is coming while I am trying to make a custom dialog for getting the update. I never got the custom dialog. The codes I have used is:\
wl_directUpdateChallengeHandler.handleDirectUpdate = ((directUpdateData, directUpdateContext) => {
WL.SimpleDialog.show('Update Avalible', 'Press update button to download version 2.0', [{
text: 'update',
handler: () => {
directUpdateContext.start();
}
}]);
});
I cant find the wl_directUpdateChallengeHandler in worklight.d.ts file either. Seeming like in ionic2 we don't have a option for custom direct update dialog. Am I right?
The version I am using is Mobilefirst V8.0.0 and Ionic2
Please help me if anyone have any better understanding on this.
How do I check in my ember 2.5 application if IE browser is being used to view my webpage by the client and if so generate an error page? I only want my customers to use firefox and chrome to view my webpage.
There are some ember addons you can use.
One of them is ember-cli-ie-check
I'm currently using Zurb Foundation 4 for a website and have had no problems with it until now.
The website i'm working on is displaying correctly on iPhone, Androids etc however on an iPad, the html tag is being restricted to a max of 768px with the content still acting responsively as it hits the edge of the iPad screen.
Is this value set in Zurb somewhere as it's currently breaking the site.
I fixed this by using modernizr to detect what device i was using. It's a weird situation as the client only wanted an iphone site but wanted the site coded to work fine independently on iPad and desktop.