Home IOS Development Facet Ratios in SwiftUI · objc.io

Facet Ratios in SwiftUI · objc.io

Facet Ratios in SwiftUI · objc.io


One of many modifiers that at all times puzzled me a bit was .aspectRatio. How does it actually work? As soon as I figured it out, it turned out to be less complicated than I assumed.

One place the place we are able to discover out loads about how SwiftUI works is SwiftUI’s .swiftinterface file. That is situated within Xcode. Inside your Terminal, go to /Purposes/Xcode.app, and carry out the next command:

								discover . -path "*/SwiftUI.framework*swiftinterface"


There are a number of variants of the .aspectRatio API, however all of them boil right down to a single implementation:

								func aspectRatio(_ aspectRatio: CGFloat?, contentMode: ContentMode) -> some View {


The variant with CGSize simply calls this technique with dimension.width/dimension.peak, and .scaledToFit and .scaledToFill name this technique with the respective content material modes and an aspectRatio of nil.

Once we name aspectRatio with a set facet ratio, e.g. .aspectRatio(16/9, contentMode: .match), the facet ratio implementation takes the proposed dimension, and proposes a brand new dimension to its little one. When the content material mode is .match, it suits a rectangle with the specified facet ratio contained in the proposed dimension. For instance, once you suggest 100×100, it can suggest 100×56.2 to its little one. Once you select .fill as an alternative, it can suggest 177.8×100 to its little one as an alternative.

I found out this habits by printing the proposed sizes. Extra on that beneath.

Maybe the commonest use of aspectRatio is mixed with a resizable picture, like so:

    .aspectRatio(contentMode: .match)


This may draw the picture to suit throughout the proposed dimension. Word that we don’t specify the precise facet ratio: it’s derived from the underlying picture.

Once we do not specify a set facet ratio however use nil for the parameter, the facet ratio modifier appears on the superb dimension of the underlying view. This implies it merely proposes nil×nil to the underlying view, and makes use of the results of that to find out the facet ratio. For instance, when the picture experiences its superb dimension as 100×50, the computed facet ratio is 100/50.

The method then continues like earlier than: when the view was proposed 320×480, the picture shall be sized to 320×160 when the content material mode is ready to .match, and 960×480 when the content material mode is ready to .fill.

Determining proposed sizes

Proposed sizes usually are not a part of the general public API of SwiftUI. Although you completely want to know how this works with a view to write efficient layouts, this is not actually documented. The one official place the place this habits is described is within the wonderful 2019 WWDC speak Constructing Customized Views with SwiftUI.

Nonetheless, there’s a hack to do that. Contained in the interface file talked about above, I looked for “ProposedSize” and located a protocol named _ArchivableView which permits us to override sizeThatFits:

								struct MySample: _ArchivableView {
    var physique: some View {
    func sizeThatFits(in proposedSize: _ProposedSize) -> CGSize {
        return proposedSize.orDefault


We are able to now merely assemble a MySample with a facet ratio and print the consequence. As an alternative of a .body, you may as well use .fixedSize() to suggest nil for the width and/or peak. Likewise, strive leaving out the primary parameter and see how .aspectRatio proposes nil to determine the best dimension of its little one view.

    .aspectRatio(100/50, contentMode: .fill)
    .body(width: 320, peak: 480)


Sadly the width and peak properties on _ProposedSize aren’t seen within the swift interface, so I had to make use of introspection to print these (and in addition add a number of helper strategies like .fairly and .orDefault). The complete code is in a gist.

If you wish to study extra about how SwiftUI works, learn our guide Pondering in SwiftUI. When your organization is already constructing issues in SwiftUI — or is about to get began — think about reserving a SwiftUI Workshop to your group.



Please enter your comment!
Please enter your name here