QML and Qt Quick

Thank you very much. It works fine now.

Finally found MapItemView which does what I am searching for.

Taken directly from the 5.15.8 docs for DisplaySettings: ========================================== Detailed Description There is no need to create an instance of this object. To use it, simply import the QtDeviceUtilities.DisplaySettings module. ========================================== But where is it? Why does it not exist for Windows? We have a commercial license. Where is this documented functionality? What is required to insure that the install of Qt that we are using includes the required library/module? In an operating room, setting the brightness is a very valuable capability. And, yes, I know what a singleton is, having created numerous singletons for this project.

It's documented in the QML Reference : https://doc.qt.io/qt-5/qtqml-syntax-objectattributes.html#property-attributes

@Narahara said in undefined reference to library function in Qtcreator: And I use a library developed by Visual Studio 201 Is this library a C++ library? If so then you have to use compiler from Visual Studio 2013 to build your app, because you can't mix binaries compiled with different compilers.

@RLocksley said in project.exe does not launch: windeployqt project.exe if that is the whole command you used, that you missed the --qmldir parameter https://doc.qt.io/qt-5/windows-deployment.html

@ekkescorner I worked on that and now it supports much more formats. Currently it's a PR opened, but it should be soon merged: https://github.com/scytheStudio/SCodes/pull/11 Sorry that I add the comment to a quite old post. I simply wanted people to know it and not be misled.

Replying here just because it's the first hit on google for Drag.Automatic: there is an answer to this question here: https://stackoverflow.com/questions/24532317/new-drag-and-drop-mechanism-does-not-work-as-expected-in-qt-quick-qt-5-3. In short, you should replace Drag.active: mouseArea.drag.active by property bool dragActive: mouseArea.drag.active onDragActiveChanged: { if (dragActive) { Drag.start(); } else { Drag.drop(); } } More details in the SO post, apparently you can see the different code flows in the QQuickDrag code. Note that Drag.Automatic does work as expected when you use a DragHandler, just not when you use a MouseArea.

If you are using this structure in other code that you don't want to change. Then I would serialize and deserialize the list. It really depends upon how interactive you want it to be. Are you planning on having the changes update in the structure based upon actions by the user? In that case I would go for a model that allows things to be updated and immediately changed in the structure. If you want to just display and update the whole thing at once you can get by using the serialize method. QML ListModel's accept javascript structures: {name: "year", value: 22} You can build this value as a QVariantList with each entry being QVariantMap. Then return QVariantList to QML. Or you can emit a QVariantMap for each member. You won't be able to get around the tedious work this involves. No matter how you do this it will a lot of copy, paste, and edit. If you are thinking of changing how you store this in your program you could store the data in a way that is easier to serialize.

@fcarney This helped me to fix the problem

@jsulm i used other gifs and any gif increments app size at least 100 mb i wanna use gif just for icon of app (just one place)

@Alisa said in Change Map language in QML Map element: MapParameter { type: "layout" property var layer: "country-label" property var textField: ["get", "name_de"] } Hi Have you found the sollution? Best Marek

@ocgltd said in How to use ItemSelectionModel with TableView: ItemSelectionModel.select | ItemSelectionModel.current It should be ItemSelectionModel.Select | ItemSelectionModel.Current

@vinci said in Q_PROPERTY typedef: Is the documentation on this out of date? What exactly are "type comparisons" in this context? Probably not out of date. I'd speculate it simply isn't telling the whole story. You can test this: Make your own typedef and do the Q_DECLARE_METATYPE and qRegisterMetatype stuff. Then try to use it as a type in the property. I suspect it should work. E.g. (split and reorder properly): namespace Test { Q_NAMESPACE enum TestEnum { MyValue }; Q_ENUM_NS(TestEnum) } using TestEnum = Test::TestEnum; class Bar : public QObject { Q_OBJECT Q_PROPERTY(TestEnum enum READ enum WRITE setEnum NOTIFY enumChanged) // ... code }; int main( ...) { qRegisterMetaType<TestEnum>("TestEnum"); // Do the QML init and such } @vinci said in Q_PROPERTY typedef: Yet types like QVariantMap are themself typedefs. E.g. QVariantMap is defined like this: Variants are very special. What exactly are "type comparisons" in this context? As in whether TestEnum is convertible to int, or other enums, or can be streamed to a binary buffer, etc. The metatype reflection stuff basically.

Were you able to figure this out? I have the same issue.