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
Hi,
my opinion is that the clazy warning should be treated as a false positive. In
general, a Q_GADGET
can't have signals (at least not with the current design of the metaobject)
system, so the warning
really doesn't make sense. So I'd say for gadgets, we should just fix clazy
(and other
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 -
On 5 Dec 2023, at 13:13, Volker Hilsheimer via Development
wrote:
On 3 Dec 2023, at 12:08, apoenitz wrote:
On Sat, Dec 02, 2023 at 11:25:16AM +0100, Giuseppe D'Angelo via Development
wrote:
On 30/11/2023 19:39, apoenitz wrote:
I propose to make this setup an official Module of Qt Creator,
