QML and Qt Quick

@mnesarco Hi mnesarco QtGraphicalEffects not available in Qt6 (qml) but we can use alternate way -> import Qt5Compat.GraphicalEffects

@inforathinam said in Clipping the child element area: Can anyone help me to achieve this? OpacityMask sounds like what you want: https://doc.qt.io/qt-5/qml-qtgraphicaleffects-opacitymask.html

System uses Wayland. For UI design reasons there're decision to move touch area (-12,-15) in reference to display area. And ... from time to time Wayland provides Touch Event not translated. Which - by Qt internals - is recognized as moved. As a solution I added evenFilter to problematic buttons with bool eventFilter(QObject *obj, QEvent *event) override { if (event->type() == QEvent::MouseMove) { QMouseEvent *ev = dynamic_cast<QMouseEvent*>(event); auto * quickItem = qobject_cast<QQuickItem*>(obj); if (quickItem && !quickItem->contains(ev->pos()) && ev->source() == Qt::MouseEventNotSynthesized && !ev->spontaneous()) { return true; } } return QObject::eventFilter(obj, event); } I could strengthen condition by adding test for touch point translation (like pos diff == (12,15)), but above solution works good enough. Still, it's workaround.

The Qt Virtual Keyboard project provides an input framework and reference keyboard frontend for Qt 6 on Linux Desktop/X11, [Windows Desktop], and Boot2Qt targets. The input framework makes it easy to write custom input methods or to integrate 3rd party input engines.

Hi, that's expected outcome. In your onPaint you clear the whole canvas area with: ctx1.clearRect(0, 0, cw, ch) on each paint event. If you remove that then the canvas is not cleared. Regards, Ulrich

Finished prototype and re-worked so it doesn't use a timer, QML: import QtQuick 2.0 import QtQuick.Controls 2.15 import QtQuick.Controls.Styles 1.4 import QtQuick.Layouts 1.3 import QtQuick.Extras 1.4 import QtQuick.Window 2.12 import SimonsCPP 1.0 Window { id: root visible: true width: 640 height: 480 title: qsTr("Playground / Staging Arena") function checkStaleStatus(strToolTip) { if ( typeof strToolTip != "string" ) { simonP.stale() return } staleIndicator.visible = (strToolTip.length > 0) hdgValue.ToolTip.text = strToolTip } SimonP { id: simonP onValueChanged: { checkStaleStatus(strToolTip) } } Label { id:hdgValue anchors.top: parent.top color: "green" font.pointSize: parent.width < 150 ? 30 : 16 text: String(simonP.value) horizontalAlignment: Text.AlignRight verticalAlignment: Text.AlignTop ToolTip.visible: ToolTip.text.length > 0 && ma.containsMouse MouseArea { id: ma anchors.fill: parent hoverEnabled: true onContainsMouseChanged: checkStaleStatus() } width: 256 } Label { id:hdgLabel anchors.horizontalCenter: hdgValue.horizontalCenter anchors.top: hdgValue.bottom color: "black" text: "HDG" horizontalAlignment: Text.AlignHCenter verticalAlignment: Text.AlignTop font.pointSize: parent.width < 150 ? 30 : 16 width: 32 } Image { id: staleIndicator visible: false anchors.left: hdgValue.right source: "/stale.svg" } Button { id: btnData text: "Click Me..." anchors.top: hdgLabel.bottom onClicked: { var currValue = simonP.value ,newValue = parseFloat(currValue) + 1; simonP.setValue(newValue); hdgValue.text = String(newValue); } } Component.onCompleted: { simonP.stale() } } SimonP.H: #ifndef SIMONP_H #define SIMONP_H #include <QObject> #include <qqml.h> class SimonP : public QObject { Q_OBJECT Q_PROPERTY(double value READ dataValue WRITE setValue NOTIFY toolTip) QML_ELEMENT private: bool mblnStale; double mdblEpoch, mdblValue; static double msdblValid; public: explicit SimonP(QObject *parent_ = nullptr); double dataValue() { return mdblValue; } Q_INVOKABLE void setValue(double dblValue); Q_INVOKABLE bool stale(); double timestamp(); signals: void toolTip(QString strToolTip); }; #endif // SIMONP_H SimonP.CPP: #include <QDateTime> #include "simonp.h" static const long sclngSecsInMin(60); static const long sclngMinsInHour(60); static const long sclngHoursInDay(24); static const long sclngMsInSec(1000); static const long sclngMsInMin(sclngSecsInMin * sclngMsInSec); static const long sclngMsInHour(sclngMinsInHour * sclngMsInMin); static const long sclngMsInDay(sclngHoursInDay * sclngMsInHour); static const char scszDelim[](", "); double SimonP::msdblValid = 5000.0; //5 seconds in milliseconds SimonP::SimonP(QObject* parent_) : QObject(parent_) { mdblEpoch = mdblValue = 0.0; } double SimonP::timestamp() { return mdblEpoch; } void SimonP::setValue(double dblValue) { mdblValue = dblValue; mdblEpoch = QDateTime::currentMSecsSinceEpoch(); //Update stale age stale(); } bool SimonP::stale() { double dblAge(QDateTime::currentMSecsSinceEpoch()); QString strToolTip; bool blnStale; if ( mdblEpoch > 0.0 ) { dblAge -= mdblEpoch; } blnStale = dblAge >= msdblValid; if ( blnStale == true ) { long lngRemaining(static_cast<long>(dblAge)); long lngDays(lngRemaining / sclngMsInDay); lngRemaining -= (lngDays * sclngMsInDay); long lngHours(lngRemaining / sclngMsInHour); lngRemaining -= (lngHours * sclngMsInHour); long lngMins(lngRemaining / sclngMsInMin); lngRemaining -= (lngMins * sclngMsInMin); long lngSecs(lngRemaining / sclngMsInSec); lngRemaining -= (lngSecs * sclngMsInSec); long lngMS(lngRemaining); if ( lngDays > 0 ) { strToolTip.append(QString("%1 days").arg(lngDays)); } if ( lngHours > 0 ) { if ( strToolTip.isEmpty() != true ) { strToolTip.append(scszDelim); } strToolTip.append(QString("%1 hours").arg(lngHours)); } if ( lngMins > 0 ) { if ( strToolTip.isEmpty() != true ) { strToolTip.append(scszDelim); } strToolTip.append(QString("%1 minutes").arg(lngMins)); } if ( strToolTip.isEmpty() != true ) { strToolTip.append(scszDelim); } strToolTip.append(QString("%1").arg(lngSecs)); if ( lngMS > 0 ) { strToolTip.append(QString(".%1").arg(lngMS)); } strToolTip.append(" seconds"); strToolTip.prepend("Stale: "); } emit toolTip(strToolTip); return blnStale; } All works great now, tool tip is shown when data is stale and mouse moves over value.

Don't create logical loops. Window { id: root width: 640 height: 480 visible: true property int myValue: 0 Slider { id: slider x: 350 y: 212 stepSize: 1 to: 10 value: myValue onValueChanged: myValue = value; } Switch { id: switch1 x: 175 y: 209 text: qsTr("Switch") checked: myValue >= 5 onClicked: { if(checked){ myValue += 5 }else{ myValue -= 5 } } } } Honestly though, you should have an indicator and 2 separate buttons to increment and decrement. Not sure what you are trying to do here.

I tried my idea above, and it seems to work (this code called from a main.qml): Item { anchors.centerIn: parent CircularSlider { id: circularSlider anchors.fill: parent ... } CLabel { id: nbr anchors { right: parent.horizontalCenter rightMargin: 3 baseline: parent.verticalCenter } text: Number(circularSlider.value).toFixed() font.pixelSize: 24 font.weight: Font.Bold } CLabel { anchors { left: parent.horizontalCenter leftMargin: 3 baseline: nbr.baseline } text: "gpm" } } Produces this: [image: 76bfd35b-2f11-4de9-ba9c-071c948ba6dc.PNG] Thanks for looking...

use QQuickWidget https://doc.qt.io/qt-6/qquickwidget.html#details thats what that is for. However, you may need to change your root component from a Window to a Rectangle or something similar

I found out that the horizontal Scrollbar was the problem, setting: ScrollBar.horizontal.policy: ScrollBar.AlwaysOff Fixed it.

@Bob64 said in Where to find?: @sierdzio apologies for the slight diversion, but what would be the modern (5.15/6) approach to this sort of import? I need to start learning about this stuff as I am going to be in the position of bringing a 5.9 project up to date soon - initially to 5.15 but ultimately to 6.x in the not too distant future. I'm not an expert on that, still stuck on Qt 5.12 on my main project now :/ But the new approach is more centered about new macros that automate this registration: https://doc.qt.io/qt-6/qtqml-cppintegration-definetypes.html#registering-an-instantiable-object-type See: QML_ELEMENT, QML_IMPORT_NAME etc.

@jsulm Thank you so much for supporting! I tried with Hercules or Terminal v.1.9 software. XCTU software only respones when receive hex and return text or hex. But probably my problem because of XCTU received/ sent type data

This is right approach. You can refer

@drmhkelley said in re-compiling (cached) qml components: Ooops - stopped paying attention for a bit, but thanks very much for the additional imformation. No problem. For your new questions: Version of Qt 5 was Qt 5.15. The app was developed starting with version Qt 4.??, but I kept it going through 5.15. Great! files managed inside a *.qrc file ... What specifically do you mean by "run your compilation"? Are you referring to the steps I specifically initiate via "make"? I meant "run qmake + make" Or do you refer to steps taken more indirectly through the QML compilation engine? That's where I start getting pretty confused. Programmers are not meant to run the QML compiler directly. Most of the time, you don't even have to think about it because qmake and make take care it it for you automatically. Also, what uses the info in the .qrc file? It is referenced in the .pro file (RESOURCES += ...), but it isn't obvious what is done with that. I don't use either qmake or CMake - never found a "simple" enough explanation/example to figure them out. Instead, I just use mingw32-make, which I've used extensively for many eons. At the core of it, qmake converts your *.pro file into a Makefile. Programmers would run qmake first, then run make. when qmake sees the RESOURCES += ... in your *.pro file, it writes the relevant rules into your Makefile to run rcc.exe. Anyway, this might be the source of your problem. rcc.exe reads the *.qrc file, collects the latest version of the resource files, and embeds them into your executable. If you have a *.qml file that isn't listed in the *.qrc file, or if your Makefile does not contain rules to invoke rcc.exe when those files are changed, then that would explain why your modified *.qml files are not getting processed. If you're running mingw32-make directly but not running qmake, that means your *.pro file is not actually getting used at all. You can probably delete the *.pro file and see no difference. "multiple versions of Qt" with single Qt Creator. When I was first starting to use Qt, I tried to do that, but was never successful. Can you point me to any simple description of how to accomplish that? Use the Qt Online Installer to install all the versions of Qt that you want (ensure that you have also installed the relevant compilers too) Create or open a project in Qt Creator. It will ask you which installed version(s) of Qt you want to use with your project, so make your selection. Click the "Run" button to build and run your application with your first selected version of Qt. Use the "Kit Selector" to select a different version of Qt, and click the "Run" button to build and run your application with that other version of Qt (see https://doc.qt.io/qtcreator/creator-building-targets.html for the diagram) That's the gist of it. Many thanks for the pointers to ports of positioning and location to Qt 6. When I first converted to Qt 6, I tried to keep up with that, but stopped once it seemed unlikely to ever reach any sensible stage of utility. I will definitely look more into whether the current status allows users like me to use them productively. Many thanks 👍

yes and I already use it, but it's a shell designed for a mouse and optimized for a touchscreen, what I'm trying to achieve is a dock specifically designed for a touchscreen I'm sorry if this is the wrong community to ask, I'll try asking somewhere else!

@JKSH using Dependencies, I found this: [image: 8ba0ed0b-a1c4-4229-a9f1-814f3946585d.PNG] It turns out that in Qt 6, the Shader tools are a separate component that must be explicitly checked during installation. I guess I'm still getting used to the more "modular" approach to Qt 6. Thanks for the help.

Hello again! I digged a little deeper into this behavior and found out, that the SwipeView actually has a clue on what's going on with its currentItem, but do not tell the world about that. Therefore I've added some more loggings and stuff to the Repeater: [...] Repeater { id: errorRepeater model: control.errorModel onItemAdded: { console.log("item added: " + item) console.log("errorview currentItem: " + errorview.currentItem) } onItemRemoved: { console.log("item removed: " + item) console.log("errorview currentItem: " + errorview.currentItem) } onCountChanged: { console.log("count changed") console.log("errorview currentItem: " + errorview.currentItem) updateItems() } signal updateItems delegate: Item { id: theItem Connections { target: errorRepeater onUpdateItems: { console.log("updateItems catched") visible = errorview.currentItem === theItem } [...] } } } With that you can see the following when an item gets removed from the Repeater: 2022-10-10_16:31:59.696 I m_ErrorModel: found item to delete: 0 (rows before: 4) 2022-10-10_16:31:59.696 D onRowsAboutToBeRemoved 2022-10-10_16:31:59.696 D onRowsRemoved 2022-10-10_16:31:59.696 D QQuickItem_QML_76(0x30211c0): repeaterIndex changed to: -1 2022-10-10_16:31:59.696 D QQuickItem_QML_76(0x3051c10): repeaterIndex changed to: 0 2022-10-10_16:31:59.696 D QQuickItem_QML_76(0x2a2e0a0): repeaterIndex changed to: 1 2022-10-10_16:31:59.696 D QQuickItem_QML_76(0x3248430): repeaterIndex changed to: 2 2022-10-10_16:31:59.696 D item removed: QQuickItem_QML_76(0x30211c0) 2022-10-10_16:31:59.696 D errorview currentItem: QQuickItem_QML_76(0x30211c0) 2022-10-10_16:31:59.696 D QQuickItem_QML_76(0x3051c10): swipeIndex changed to: 0 2022-10-10_16:31:59.697 D QQuickItem_QML_76(0x2a2e0a0): swipeIndex changed to: 1 2022-10-10_16:31:59.697 D QQuickItem_QML_76(0x3248430): swipeIndex changed to: 2 2022-10-10_16:31:59.697 D count changed 2022-10-10_16:31:59.697 D errorview currentItem: QQuickItem_QML_76(0x3051c10) 2022-10-10_16:31:59.697 D updateItems catched 2022-10-10_16:31:59.697 D updateItems catched 2022-10-10_16:31:59.697 D updateItems catched 2022-10-10_16:31:59.697 D QQuickItem_QML_76(0x3051c10): visible changed to: true (w: 640 | h: 200) 2022-10-10_16:31:59.697 I errorModelChanged catched As you can see, does the errorview's currentItem change after the SwipeIndex' of the items have been updated and the count of the Repeater items changes. The logged currentItem then is the one that I actually want to be visible and it is the one with SwipeView.index of 0. I then going to send a signal to update the visibility of the actual currentItem... BUT... the result is still the same :( Sometimes the item is visible, sometimes it is not. It's a mess. Regards, matzze