https://bugs.kde.org/show_bug.cgi?id=455789
b...@mogwai.be changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |b...@mogwai.be
--- Comment #3 from b...@mogwai.be ---
(In reply to ratijas from comment #1)
> The new code mixes declarative bindings with imperative function with
> side-effects (console warn). The two don't play nicely together, as the
> order of signals propagation is not defined.
I'm pretty sure the propagation in this particular case is well-defined. And
it's defined in such a way that that warning/side-effect will always happen:
In controls/templates/SwipeListItem.qml, listItem has leftPadding and
rightPadding which require overlayLoader.paddingOffset. This will cause
overlayLoader to be created in order to evaluate overlayLoader.paddingOffset.
This in turn will trigger the validate function; however, at that point
listItem.leftPadding and/or listItem.rightPadding have not yet been set since
this whole chain of events has been set in motion in order to set those
paddings in the first place. Hence, the warning is printed and the binding is
forced even before it has been set the very first time.
--
You are receiving this mail because:
You are watching all bug changes.
