Re: [Development] Documentation and Q_GADGET / Q_PROPERTY

2024-01-15 Thread Ulf Hermann via Development
The one thing where you need NOTIFY or BINDABLE is if you want to expose a class as a type to QML AND you want to make its instances usable in bindings; I believe that's where the warning originates from. However, that's not your use-case, so it shouldn't matter. Value types do not need

Re: [Development] Documentation and Q_GADGET / Q_PROPERTY

2024-01-15 Thread Fabian Kosmale via Development
Christian Ehrlicher via Development Gesendet: Montag, 15. Januar 2024 20:49 An: development@qt-project.org Betreff: [Development] Documentation and Q_GADGET / Q_PROPERTY Hi, In the sql module I've some classes which do not derive from QObject but have a lot of setters/getters. For a nicer

[Development] Documentation and Q_GADGET / Q_PROPERTY

2024-01-15 Thread Christian Ehrlicher via Development
Hi, In the sql module I've some classes which do not derive from QObject but have a lot of setters/getters. For a nicer documentation without duplicating information I had the idea to convert them to properties. So I added Q_GADGET and a simple Q_PROPERTY with only a READ and WRITE property -