QML and Qt Quick

No. This signal is emitted when the scene graph has been invalidated. This signal implies that the opengl rendering context used has been invalidated and all user resources tied to that context should be released. The signal just informs you that the scene graph has been invalidated and that the OpenGL context has been released. Have a look at this "page.":http://doc-snapshot.qt-project.org/5.0/qtgui/qopenglcontext.html. If the context is temporarily not needed, such as when the application is not rendering, it can be useful to call destroy() to free resources. However, if you do so you will need to call create() again before the context can be used, and you might need to recreate any OpenGL resources and reinitialize the OpenGL state. You can connect to the aboutToBeDestroyed() signal to clean up any resources that have been allocated with different ownership from the QOpenGLContext itself. Have you confirmed that this is in fact your problem. Have you checked that this signal is being emitted? If not then my suggestions might not be so helpful.

Yes that is true. You can get a texture from a "QQuickItem":http://qt-project.org/doc/qt-5.0/qtquick/qquickitem.html only if it is a "textureProvider":http://qt-project.org/doc/qt-5.0/qtquick/qquickitem.html#textureProvider. At a quick glance, there doesn't seem to be anything that exposes an objects' pixmap.

Have a look at the solution posted "here":http://qt-project.org/forums/viewthread/26191/P15.

Yeah I thought there must be a more direct approach to this, I just couldn't find anything in the docs. Thanks Chris.

main.qml import QtQuick 1.0 import QtWebKit 1.0 Rectangle { id:main width: 1280 height: 800 Button{ id: button height: 50 width: 100 anchors.centerIn: parent onButtonClicked: { console.log("Mouse was clicked"); brow.visible = true; brow.urlString = "some url with flash plugin"; console.log("url:",brow.urlString); } } WebBrowser{ id: brow visible: false } } WebBrowser.qml: import QtQuick 1.1 import QtWebKit 1.0 Rectangle { id: webTray width: 1280 height: 800 property string urlString: "" Button { id: callaccept y: 0.01*webTray.height anchors.right: webTray.right; anchors.rightMargin: 0.05*webTray.width displayText: "Quit"; width: 0.05*webTray.width; height: 0.04*webTray.height; onClicked: { console.log("clicked on quit"); brow.visible = false; brow.urlString = "" console.log("browser is visible?:",brow.visible); } } Rectangle { width: webTray.width; height: 2; color: "silver"; anchors.bottom: web.top; } height: 50 width: 100 anchors.centerIn: parent onButtonClicked: { WebView { id: web preferredWidth: webTray.width preferredHeight: webTray.height - 0.06*webTray.height; y: 0.06*webTray.height transformOrigin: Item.TopLeft settings.pluginsEnabled: true url: webTray.urlString smooth: false onAlert: console.log(message) } }

Ok, thanks. It's fixed and thread can be closed.

Thanks guys - I can't update to a prerelease version of Qt for this project (in fact, one of the platforms that I'm developing for is actually on Qt 4.6 and will require special qwidget-based forms rather than the spiffy new qml forms I'm building). I guess if this doesn't work easily with 5.0, then I'm pretty solidly on 4.8. I'll try building what's in the public repository on gitorious for 4.8.

Thanks a lot! It really works as supposed now. Thank You.

ps - I dont see the same stuff when running valgrind on minehunt

Bug reported with sample project here: https://bugreports.qt-project.org/browse/QTBUG-30810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel

MouseArea is not suitable for multitouch. They only handle mouse events. Try "MultiPointTouchArea":http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-multipointtoucharea.html for touch events. There is also "TouchArea":http://qt.gitorious.org/qt-labs/qml-toucharea/ for Quick1

this doesn't work for me. The program didn't find the file. Perhaps this is because of my mac system. But in Qt Creator this is an error, too.

weiyuemin: That worked. thanks!

Thanks maxus for posting your find! It makes sense now.

Put your javascript logic that populates your controls in the QML source or pass the QML item reference (id) over to your javascript librarys functions as an argument?

Too bad there is no childAt() method in QML.