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
Properties like contentAlignX/contentAlignY or anchorX/anchorY should have a common property.
align: left, top;
//would be equivalent to
alignX: left;
alignY: top;
contentAlign: center;
//would be equivalent to
contentAlignX, contentAlignY: center;
The text was updated successfully, but these errors were encountered:
I'm against this on the basis that when a property accepts multiple values, it should accept an indefinite amount of values. It's the 0-1-infinity rule. We could consider using an align property which takes something like a @point object. It would look like this:
align: @{ x: left; y: top };
//equivalent to
align.x: left;
align.y: top;
//also equivalent to
align: @{ left; top };
It's not always the case (take the corners property on @Rectangle for instance).
I really think it's something CSS users will miss. We should provide a way to achieve what they want while internally dealing with it (using an object if needed). I am still supporting it because such a shorthand will be expected and covers a basic use case (positioning).
Properties like contentAlignX/contentAlignY or anchorX/anchorY should have a common property.
The text was updated successfully, but these errors were encountered: