Open joshpoll opened 1 year ago
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
.
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.