QML and Qt Quick

Can you post the sample code that you created ? So that we can understand clearly.

Hi, sorry for the late reply. I looked at your code and no, it's not the effect i needed. What i needed was the rotation of the path view as if it were the mouse dragging it. I tried to obtain this effect by injecting the mouse movement into my application via c++ but it didn't give me the right feel so i went for a repeater item. I set the repeater to follow the arc i needed and acted upon its angle, thus obtaining the desired effect. Thankyou for your time

It's work! Thank p3c0! Thank you very much!

I recompiled my program with console enabled. It's showing this output when QQuickWidget is shown (no output directly after start): C:\Users\Vendelin\Downloads\Deployment>qq_pokus.exe OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr OpenGL Warning: crPixelCopy3D: simply crMemcpy'ing from srcPtr to dstPtr err:[0xa04]:d3d:D:\tinderbox\add-4.3\src\VBox\Additions\WINNT\Graphics\Wine_new wined3d\resource.c 218: Resource 041F0FD0 is being unloaded while mapped. When it's run for the second time, it's showing QML scene properly, but prints the same error message.

Hi and welcome to devnet, This package not being part of the Qt distribution, you should rather contact the authors of QtGStreamer, you're more likely to get a quick answer there

Does the youtube video help? (Try fast forwarding to 38 minutes, I think..) "https://www.youtube.com/watch?v=XvKDUWPA9O4":https://www.youtube.com/watch?v=XvKDUWPA9O4

Alternatively, you can solve this using only qml; this has the advantage that the qml content is initially rendered in an already fullscreen window and signal onWindowStateChanged is not called twice: @ import QtQuick.Window 2.2 // Window.FullScreen import QtQuick.Controls 1.3 // ApplicationWindow // Note for OS X: using Window instead of ApplicationWindow only hides the dock (and shows it again when app is quit) ApplicationWindow { id: mainWindow visible: true // this is mandatory visibility: Window.FullScreen onWindowStateChanged: { console.log( "onWindowStateChanged (Window), state: " + windowState ); } } @

[quote author="p3c0" date="1421902957"] Yes that is also a right way. For other approaches you can check "this":http://doc.qt.io/qt-5/qtqml-cppintegration-interactqmlfromcpp.html doc.[/quote] Thanks very much.

On the bright side support for video on iOS with Quick may come in Qt 5.5, so stay tuned.

dxdiag both over Remote desktop and on the broken machine shows DirectX 11. My application isn't printing anything relevant to console. I also added this code: @ connect(this, &QQuickWidget::sceneGraphError, [this](QQuickWindow::SceneGraphError reason, const QString &msg) { QMessageBox::critical(this, "Error", msg); });@ and expected to get some error message on the computer with the broken graphics driver, but I get nothing. It looks like "QTBUG-36065":https://bugreports.qt.io/browse/QTBUG-36065 is still present in my case, although it's marked as fixed. I'd really like to show the user at least an error message when this happens.

Just in case if someone came across a similar situation he/she may understand that this post has a solution.

Replying to share my personal experience with this issue. Changing the ownership of the instantiated object to "QQmlEngine::CppOwnership":http://doc.qt.io/qt-5/qqmlengine.html#ObjectOwnership-enum before returning it indeed fixes the issue. What is not very intuitive though is the fact that you have to change the ownership to CppOwnership even if the objectOwnership() method already returns CppOwnership. This gives something like: @QObject * MyClass::InvokableMethod ( ... ) { QObject * pObject = InstanciateObject( ... ); QQmlEngine::ObjectOwnership ow = engine->objectOwnership( pObject ); // Here, ow == QQmlEngine::CppOwnership engine->setObjectOwnership( pObject, QQmlEngine::CppOwnership ); return pObject; }@ The "setObjectOwnership()":http://doc.qt.io/qt-5/qqmlengine.html#setObjectOwnership and "objectOwnership()":http://doc.qt.io/qt-5/qqmlengine.html#objectOwnership methods seem to perform more stuff than just set and get a two-value property on the object, something that does not appear in the documentation. Anyway, thanks for the post.

Try changing to... @Window { id: root width: 200 height: 200@ or maybe set/use the minimum/maximum width and height properties IDK but I think if you don't set the properties, they may default to 0

[quote author="ondrejandrej" date="1421762292"]Can I avoid copying those files e. g. by adding them to resources?[/quote]Interesting idea; I've never tried putting official files in a resource before. You could try it, but I'm not sure if the LGPL license allows that. If you have the "Professional license":http://www.qt.io/download/ you could use the Qt Quick Compiler to convert your QML source code into your program binaries.

Hi, QDeclarativeView is for Qt Quick 1. These are old technologies which are now deprecated. Use QQuickWidget + Qt Quick 2 instead. See "Porting QML Applications to Qt 5":http://doc.qt.io/qt-5/qtquick-porting-qt5.html for more info.

Hi, I don't know why, but the Qt engineers do. You can find them at the "Interest mailing list":http://lists.qt-project.org/mailman/listinfo/interest (You need to subscribe first)

yes, install apt-get install xserver-xorg-video-intel libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core [quote author="sierdzio" date="1421827439"]Do you have OpenGL drivers installed?[/quote]

Once again I shoot myself in the foot. I'm posting this for the benefit of everyone else since it was such a stupid thing that I did: qRegisterMetaType<QObject*>("QQuickitemLayer"); What's going on here (as far as I can tell) is that QObject* was bound to the name QQuickItemLayer in the Qt Meta Object system. The issue with this is that the subsequent QML elements are registered also using these same types. I know this is a vague explanation- but it boils down to the meta type system. Taking this line out in my code fixed the issue I was seeing. I'm writing a blogpost elsewhere to fully explain some of the things I tried since a lot of it is off topic. The reason I put this line of code in was that the QmlEngine was reporting that this was an issue in a console app. I thought I was being clever by providing this type (it silenced the console errors). However, it just caused a bigger issue.