https://bugs.kde.org/show_bug.cgi?id=438610
Ismael Asensio <isma...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |isma...@gmail.com
--- Comment #20 from Ismael Asensio <isma...@gmail.com> ---
(In reply to Nate Graham from comment #19)
> Ah, the problem is that Logic.conectedDevicesCount() is imperative, and not
> a property. So when that changes, the UI code doesn't get notified and
> updated itself as it should.
I've been playing with this for a bit, and I'm mostly convinced that this is an
upstream issue on how sections are created, possible due to optimizations.
It seems that when creating the new "Connected" section, a copy of the other
one is first made, and then the properties get updated, which results in the
visual glitch. This is what happens when connecting a new device.
// This is the "Available" section loader
qml: ** Loader.onActiveChanged() ID: QQuickLoader(0x55c6450a4800) section:
Available connectedDevices: 1 active: true
// This is the "Connected" section loader. But it starts as "Available"
qml: ** Loader.onActiveChanged() ID: QQuickLoader(0x55c6450a3480) section:
Available connectedDevices: 1 active: true
qml: ** Loader.onActiveChanged() ID: QQuickLoader(0x55c6450a3480) section:
Connected connectedDevices: 1 active: false
All the things I've tried didn't make the glitch go away:
- Refactoring the applet to use properties instead of imperative code doesn't
fix the issue.
- Playing with the height and active properties to change the order of
evaluation
- Using the Connected property instead of the proxy Section, so we're sure the
sorting and the sections are in sync.
--
You are receiving this mail because:
You are watching all bug changes.
