I agree with Giuseppe and I would like to add to it the fact that
properties are restored in what I could guess as alphabetical order, which
in itself already causes problems for custom widgets.
That said, when developing custom widgets developers must pay attention to
this fact of properties that
In this case why keep it around?
Keeping something that does not work only generates more confusion (like
this post).
Could at least a note at the official documentation be added stating that
the method generates an invalid UI file and it must not be used?
On Mon, Oct 28, 2019 at 1:07 AM Friedema
Hi,
Just a little follow up. Can this (invalid widget being generated by
QFormBuilder.save ) be considered a Qt issue and fixed?
The "all properties changed" is not a big deal, the incorrect form is.
Thank you,
Hugo
___
Development mailing list
Developm
lopment mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
>
--
Hugo Slepicka
*hhslepi...@gmail.com *
*+1 631 855 5717*
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Hi Qt Developers,
Thank you for your amazing work at this library.
This message is a cross-posting with the Qt Forum (
https://forum.qt.io/topic/107830/issues-with-qformbuilder-all-properties-modified-invalid-ui)
more detailed information can be found there as well as pictures showcasing
the Desi
