https://bugs.kde.org/show_bug.cgi?id=368493
David Edmundson changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=368493
--- Comment #4 from Eike Hein ---
David, did we fix this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368493
--- Comment #3 from David Edmundson ---
binding loop:
start
break QQmlAbstractBinding::printBindingLoopError
for every frame with QQmlBinding::update()
call this->expressionIdentifier()
TRACE:
#0
https://bugs.kde.org/show_bug.cgi?id=368493
--- Comment #2 from David Edmundson ---
That's not how the binding loop detection works.
It's a runtime recursion check in updating the binding, emitted if you update
it from within trying to update itself. It's not a check
https://bugs.kde.org/show_bug.cgi?id=368493
--- Comment #1 from Eike Hein ---
I was thinking binding loops are false positives because the checker isn't
evaluating "vertical" and just naively checking the operand references.
Anyway looks credible that this issue is the Pager ...
https://bugs.kde.org/show_bug.cgi?id=368493
David Edmundson changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |h...@kde.org
--