We currently offer multiple Properties that offer multiple input fields. Such examples include the 'Margin', 'Padding', and 'Corner Radius' Properties.

The ability to set the fields they offer individually offers an absolutely critical level of customization to UI Elements.
Likewise, our Binding system is a cornerstone of powerful, dynamic interface design within Studio.

However, currently, Bindings can only be employed on a Margin, Padding, or Corner Radius Property if the same value is used across all four of its fields. (or if the Binding is bound to a similar 2x2 Matrix, which the vast majority of Elements don't offer -- almost all numerical values are a single number.)

This restriction makes it impossible to for example, to set a Left Margin to be equal to the <ActualWidth> of another Element.

I realise this is a far more consequential change than just the Studio UI, since its a "that's how it works in WPF" thing, but I've run into this is as a blocker to what I wanted to achieve enough times that I wanted to get this on paper, for us to potentially evaluate/discuss further.

Very quick/rough proposal attached as image. In this scenario, users could elect if they wanted to Bind to all 4 fields simultaneously (as it works now), or Bind individual fields to individual values (in which case the 4-Way Binding as it works now, would be removed in favour of the individuals)