[Development] Issues with QFormBuilder - All properties modified & Invalid UI
giuseppe.dangelo at kdab.com
Tue Oct 29 12:56:08 CET 2019
On 29/10/2019 12:29, Jaroslaw Kobus wrote:
> > Sorry, I'm lost now. If you store them both and apply them in either
>> order, shouldn't the result be correct no matter what?
> That doesn't matter in fact. If you change orientation first, then
> sizePolicy, you get the state
> which can't be reliably stored / read, unless you explicitly know that
> there is
> hidden dependency (if you know, you may influence the order or storing /
> but still it's not orthogonal).
I agree on the possibility, but this is still a bug in those classes or
a missing feature: one needs to know that a property has not been set
manually by the user to avoid overwriting it, or, well, to avoid
serializing it in the first place.
Given this is not being done consistently across Qt and/or the meta
object system lacks these informations, this is all pointing towards
deprecating QFormBuilder as a "real" utility and being more like some
just quick-glue code lacking a robust use case.
My 2 c,
Giuseppe D'Angelo | giuseppe.dangelo at kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4329 bytes
Desc: S/MIME Cryptographic Signature
More information about the Development