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
The position type is derived from the matching position type of it's nearest parent that has a defined position type.
The highest parent must have an explicit position type as they have no parent. In such a case, absolute and relative positioning will both have the same effect on that crate's final position.
F.i : a(pos=["12A","32A"]) > b(pos=[8,4]) > c(pos=["R","R"]) > d(pos=[4,4])
Here, B's position types are absolute for both axes as defined by it's nearest parent. C redefines it's position as relative for both axes, thus D will be placed 4 units relative to C.
Defining the relation in the attribute value itself turned out not to be that great of an idea ; it has therefore been scrapped in favour of value types. As in, data types.
From now on, and likely forever :
int : value in pixels
float : relative to parent's corresponding attribute
Position mode does no longer cascade nor propagate to a crate's children.
As a temporary byproduct, this also fixes having to declare attributes as strings.
No description provided.
The text was updated successfully, but these errors were encountered: