We have a general lack of two-way bindings (and for a reason, they're
not trivial in async world). Using Binding { } is preferable over
assignment in a signal handler, though.
And yeah, the original binding is destroyed because the component
assigns a value to its "checked" property, so the binding has nowhere to
"live" any more. Having an explicit Binding { } object works around
this. Because "checked" changes onClick anyway, you should probably use
a Binding the other way, too, instead of assigning to
systemSettings.rotationLock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390643
Title:
Orientation lock switch doesn't notice gsettings changes
To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-qt/+bug/1390643/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
