You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2021. It is now read-only.
This is because each of these is a distinct property instance. This can be confusing to the end user. The "hack" fix is to always use the same property and apply constraints on it instead, e.g. position.x() and position.y().
Ideally the positionX and positionY properties would react to changes to position.
Note that changes to positionX and positionY do propagate to position because they use externalWrite to adjust the position property.
Resolving this would probably be a matter of having property do an external write to positionX and positionY, so long as this didn't cause a retain cycle.
The text was updated successfully, but these errors were encountered:
This is because each of these is a distinct property instance. This can be confusing to the end user. The "hack" fix is to always use the same property and apply constraints on it instead, e.g.
position.x()
andposition.y()
.Ideally the positionX and positionY properties would react to changes to
position
.Note that changes to positionX and positionY do propagate to
position
because they use externalWrite to adjust theposition
property.Resolving this would probably be a matter of having
property
do an external write to positionX and positionY, so long as this didn't cause a retain cycle.The text was updated successfully, but these errors were encountered: