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 Sep 16, 2024. It is now read-only.
This suggests that the Circle's position should be set before it is read by the Row to be consistent. But actually this is not quite right, since Row can translate its children around. Maybe instead we can have
This would probably set the translation of the Row to 0 to match the behavior of lazy materialization. We could also think of it as removing that coordinate system entirely. But this introduces additional complexity in the Ref version where the difference in positioning modes doesn't really make sense, since it's always absolute.
SwiftUI doesn't seem to do anything sensible in these cases, so it's hard to look there for answers.
The text was updated successfully, but these errors were encountered:
A simple option could just be to expose a translation field, but it's not clear how that would compose with x and y fields on e.g. Row. Another option could be to rename positioning to coordinates or coordinateFrame.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What should the behavior be when children of a Row have positions?
I think these two specs should be equivalent:
This suggests that the Circle's position should be set before it is read by the Row to be consistent. But actually this is not quite right, since
Row
can translate its children around. Maybe instead we can haveThis would probably set the translation of the
Row
to 0 to match the behavior of lazy materialization. We could also think of it as removing that coordinate system entirely. But this introduces additional complexity in theRef
version where the difference in positioning modes doesn't really make sense, since it's always absolute.SwiftUI doesn't seem to do anything sensible in these cases, so it's hard to look there for answers.
The text was updated successfully, but these errors were encountered: