@raven-worx
mmh, I'm unsure but I'll look into it.

However that gave me an idea. The TextInput QML-Item should have it's own c++ class(I'm however unsure what it's called), somewhere with QQuickItem as it's very base class.

I could look into creating my own myTextInput Item that handles the QInputMethod-Query

@raven-worx Thanks, I will try that. I let you know if it works or not.

@sierdzio. Thanks a lot for your answer.

@milan said in How to add qml to mainwindow ui file:

Can somebody help me how to add qml to mainwindow ui. I added a QQuickwidget in mainwindow.ui from designer.

Then I added following code:

QQuickView *qmlView = new QQuickView(); qmlView->setSource(QUrl::fromLocalFile("test.qml")); ui->widget->createWindowContainer(qmlView, this);

If you added a QQuickWidget via designer, why adding anoher QQuickView via code!?

just access your QuickWidget and set the source:

ui->quickWidget->setSource(QUrl(QStringLiteral("qrc:/test.qml")));

Hi @Morten,

Thanks for the report ! Could you add a minimal compilable example to it ? That would allow developers to more easily reproduce the problem and search for a solution.

Thanks, I did try createWindowContainer and it works fine but I was expecting that QQuickWidget would work too given that it's recommended before createWindowContainer. Also it seems like the same problem happens when using QOffscreenSurface with QQuickRenderControl for the same qml with canvas3d.

After further testing with the QQmlEngine::addImportPaths(), QQmlEngine::addPluginPaths(), QQmlEngine::setImportPathList() and QQmlEngine::setPluginPathList() functions none of these allowed the QtQuick and QtQuick.Controls qml modules to be found and installed.

I then added the QML2_IMPORT_PATH environment variable and set it to point to my Qt build qml folder D:/qt-5.5.1_vs2012x64/qt_build/qtbase/qml and this worked.

Question is why don't the paths added by the QQmlEngine functions work? The paths are added but don't seem to be searched.

Great tip! No, using QQuickWidget seems to solve the problem!

Thank you very much, now it works fine :-)

Here is the solution:

ui->gauge_quick->setSource(QUrl(QStringLiteral("qrc:/qml/QtQuickProgressBar.qml"))); ui->gauge_quick->show(); auto rootObject = ui->gauge_quick->rootObject(); connect(this, SIGNAL(setGauge(QVariant)), rootObject, SLOT(setvalue(QVariant))); emit setGauge(15.5);

@maximo
Ok :)
I think to get it to repaint itself is easy for Quick experts
but if this works for you, then its ok, i guess.

Hi and welcome to devnet,

To discuss such matters, I'd recommend posting on the interest You'll find there Qt's developers/maintainers (This forum is more user oriented)

@MrKozmon

I'm having the exact same problem on Android. When I drag a QQuickWidget that is hosting a QML-based WebView on Android, the widget moves but the WebView is left in the original position. Wondering if there has been any progress or a workaround for this issue.

I am using Qt 5.10.0, developing for an x86 Android platform.

@xumuk As said earlier it is a limitation. But if you still need it you should have a look at the 2nd and 3rd paragraph in the link which I posted earlier. Basically you will have to do this:

QQuickWidget *wd = new QQuickWidget(this); wd->setAttribute(Qt::WA_AlwaysStackOnTop); wd->setClearColor(Qt::transparent); //and the opacity can be set in QML istelf for eg. for a Rectangle Rectangle { width: 300 height: 300 color: "green" opacity: 0.5 }

If you load this QML in the QQuickWIdget and put a QWidget in background it should be visible.

@p3c0 This isn't what i'm trying to do. Setting the whole item as the drag.target would make the item follow the cursor and since the item can't be drawn outside of the Qml scene it would clip as soon as the pointer leaves the dock. I use a non visual "draggable" Item to be the drag.target like in the externaldraganddrop example.

I tried what you suggested and noticed something strange however.

Inside a QQuickWidget : the item will not follow the cursor during the drag and drop but follow it after the user releases the mouse button ("locking" the mouse in the process). MouseArea.onReleased is not called after the drag and drop.

Inside a full Qml application : the item will not follow the cursor during the drag and drop but move to the cursor when the user releases the mouse button. MouseArea.onReleased is called after the drag and drop.

Edit : I just found a bug report for the same behavior (https://bugreports.qt.io/browse/QTBUG-40773).