QML and Qt Quick

@sierdzio Thanks!

@J-Hilk said in Qt6 : how to use QtQuick.Control v1.4? (for the old TreeView): We can't upgrade to Qt6 with all the modules that we need, and that currently aren't even all available yet Qt 6.2 comes end of the month and then catches up with the modules compared to Qt 5

@eyllanesc @KroMignon Thks. onClicked: { img.cache = false; img.source = "" img.source = "file:///Volumes/D/x.png" } In this way, the update must first set "cache=false" to work. But if set "cahce=true" after the update, the image will return to the old one.

@Swati777999 What you point out is wrong. QPaintDevice is a class that is painted using QPainter, and from that class QWidget, QImage, QPixmap, etc. inherit. Please read the docs: https://doc.qt.io/qt-5/qpaintdevice.html

Cool. I change the code according to your comments. the issue is gone/fixed. Thanks for your help. I thought when I imported the control version 2.12 "import QtQuick.Controls 2.12" , it should include all controls that come before this version. Now I realized I should import the exactly version number like what the document mentioned. In Android there is one concept like API level, It is convenience. I guess if implement the control like this will make development easier.

Thank you very much. Now i will read and look all the links. Thank you.

@GrecKo thank you! That is what I was looking for!

@SGaist Hi, I'm trying to achieve something like this: https://youtu.be/FabJx0Bo1pg?t=226 using the incorrect tool do you mean incorrect widget?

Actually I tried it fast and after setting some qDebug it seems I never received the touch events. I did what is suggested in this answer : https://stackoverflow.com/a/34740261 And now I am able to get the touch events and add "QApplication::processEvents();" But there is no difference the problem is still here. With this debugging, I saw that touch event are received even when the application is in the buggued state (black screen). They seem processed as usual, because when I hit Ctrl+Alt+Suppr, and my Window reappears, I see the result of the touch event in the GUI. Some more investigation on the Windows side showed some incompatibility with the Intel Graphics Driver. The tablet is equipped with an Intel HD Graphics 620. The app works with the driver Intel Graphics Driver 23.20.16.4973, which is a "DC" driver, now called "Legacy" The bug appears with the Intel Graphics Driver 26.20.100.7637 which is a "DCH" driver introduced with the "Universal Window Platform" https://www.intel.com/content/www/us/en/support/articles/000031572/programs/intel-corporation.html Installing the "Legacy" driver on the Windows 10 Iot Tablet fixes the problem. But this is not a really good fix, at it implies to keep this driver version and does not permit updates. Are they specific known issues with QML and Intel Graphics Driver DCH ?

@fcarney Got it thank you so much :)

The model should provide this information for you. Create a role in the model which will return the correct value for any given cell. On QML side, just access that role and display it directly. No need for any get() method (which, by the way, is called data() https://doc.qt.io/qt-5/qabstractitemmodel.html#data, not get()).

@kitfox said in How do you specify values for a ComboBox?: Yes I have. It didn't help. Like I said in my post, the second form isn't displaying anything. Then you don't have read it carefully, you have to define textRole and valueRole, cf https://doc.qt.io/qt-5/qml-qtquick-controls2-combobox.html#combobox-model-roles: ComboBox { textRole: "text" valueRole: "value" id: gridCombo model: [ { text: firstValue, value: firstValue }, { text: secondValue, value: secondValue }, { text: thirdValue, value: thirdValue } ] }

@ocgltd add contentHeight: input.contentHeight to your Flickable

I don't see a ready-made solution. You could pass the ScrollView to the QQuickPaintedItem, or look for it by following the parentItem chain. Use the underlying Flickable's contentX, contentY, etc, and QQuickItem::mapRectFromItem() to determine what portion of the QQuickPaintedItem is visible. Calls to update() will be necessary when the ScrollView's viewport changes, because the initial paint is expected to have painted the entire item into the backing store.

@ffhguy Hi, did you solve this problem? I'm facing exactly same thing now.

@GrecKo Thx, i will try these solutions

@nishiokas Please don't introduce setAttribute() or setTagName(), they are not what you want and just unnecessarily complicate the code. element.setNodeValue("http://1.2.3.4:8000/common-shop/"); If I am not mistaken, <commonPrimaryUri> does not directly have the value. Rather, it has a child node, of type QDomText, which has the text you want to alter. Try enumerating <commonPrimaryUri>'s children to see if I am right.