Hi Alberto,
Firstly, this is a really interesting topic, so thanks for bringing it up, and
even more thanks for offering to help investigate and implement changes!
Secondly, this problem is one that we have considered before, and the ideal
solution is probably some "binding is dirty" flag, combi
On 03/05/2012 03:39 AM, Alan Alpert wrote:
> It's pretty much as you described. With the slight addendum that what you're
> asking for is probably not possible (in the general case). X and Y are
> independent variables, one may change without the other. So the code can't
> just wait for a signal
On Sun, 4 Mar 2012 03:15:40 ext Alberto Mardegan wrote:
> Hi all,
> sorry for the intricated subject, I couldn't find a concise and
> understandable way to express what I mean. :-)
>
> Often it happens to me that I want to run some code when two or more
> properties change on a QML object. A rea
Hi all,
sorry for the intricated subject, I couldn't find a concise and
understandable way to express what I mean. :-)
Often it happens to me that I want to run some code when two or more
properties change on a QML object. A real life example is the contentX
and contentY properties from Flickabl
