Setting .enabled: false is a worthy suggestion, but I think that would make the problem slightly worse, not better. Animating from disabled×unchecked to enabled×checked would be even more noticeable — and therefore even more distracting — than from enabled×unchecked to enabled×checked.
Having an “unknown” state would work (the micro equivalent to a “skeleton screen” for a screen as a whole), but it seems a bit excessive. It would be a 1/3 increase in visual design work for checkboxes and radio buttons, and a 50% increase for switches, for something that is not only seldom seen, but also, when it is seen, is seen only for a fraction of a second. So, I still think a better approach would be simply not to show the control at all until its value is known. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1276066 Title: Checkbox needs 'unknown' state Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: The Checkbox component always animates its state transitions. Sometimes, the "checked" property is set shortly after initialization, which shows the animation when creating a page. For example, this happens when using the GSettings object, which fills in its properties in its componentCompleted: GSettings { id: settings schema.id: "com.ubuntu.touch.system" } CheckBox { checked: settings.autoBrightness } It would be nice if there was a property "animate" which could be used to suppress animations while loading a page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1276066/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
