https://bugs.kde.org/show_bug.cgi?id=368493
--- Comment #3 from David Edmundson <k...@davidedmundson.co.uk> --- binding loop: start break QQmlAbstractBinding::printBindingLoopError for every frame with QQmlBinding::update() call this->expressionIdentifier() TRACE: #0 file:///opt/kde5/share/plasma/plasmoids/org.kde.plasma.pager/contents/ui/main.qml:224:42 #1 file:///opt/kde5/share/plasma/plasmoids/org.kde.plasma.pager/contents/ui/main.qml:225:44 #2 file:///opt/kde5/share/plasma/plasmoids/org.kde.plasma.pager/contents/ui/main.qml:224:42 #3 file:///opt/kde5/share/plasma/plasmoids/org.kde.plasma.pager/contents/ui/main.qml:54:19 The binding loop: - anchors.fill changes the size - this causes rowHeight to re-evaluate (a correct behaviour) - this signals it has changed (a correct behaviour) - this calls columnWidth to re-evaluate (a correct behaviour) - this signals it has changed (a correct behaviour) - this causes rowHeight to re-evaluate (a correct behaviour) - BAM, binding loop. So: 1) I was right that it *is not* a false positive, as it has actually looped 2) You are right that *it is* a false positive, as you weren't going to do anything with the new evaluation, and rowHeight would not update on the second round Though this also shows that the binding loop isn't anything to do with my original bug. -- You are receiving this mail because: You are watching all bug changes.
