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.
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
positionbecause they use externalWrite to adjust thepositionproperty.Resolving this would probably be a matter of having
propertydo an external write to positionX and positionY, so long as this didn't cause a retain cycle.