https://bugs.kde.org/show_bug.cgi?id=484541
--- Comment #2 from orblazer <orblazer.minecraft+...@gmail.com> --- (In reply to ratijas from comment #1) > That tends to happen when you build an architecture that relies on magic > reflection a bit too much. Also QQmlComponent lacks needed introspection to > determine the set of available properties of its loaded type. Yes and for explain the issue i have simply use an official plasmoid. In the idea the `cfg_*` is really useful but since we need dynamically load the component that become an nightmare to predict. For me the only 2 ways to deal with that in QML (i think an another way exist with a bit of C++) is : - load the page before set the props : It's not great because is generate re paint due to changes - load once in "dummy" mode and filter variable from that (that also generate errors if the config page doesn't support "null" values) An other way but it's create an big broken is to re change the way to manages settings and store in in single `QtObject` (but i think that could also make some issues with nested object (especially an flat array like `[0, 1, 2]`), if the serializing of `QtObject` is same of `ListModel`) -- You are receiving this mail because: You are watching all bug changes.
