{"id":40240,"date":"2023-08-03T19:40:15","date_gmt":"2023-08-03T23:40:15","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=40240"},"modified":"2023-08-03T19:41:04","modified_gmt":"2023-08-03T23:41:04","slug":"how-nshostingview-determines-its-sizing","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/08\/03\/how-nshostingview-determines-its-sizing\/","title":{"rendered":"How NSHostingView Determines Its Sizing"},"content":{"rendered":"

Brian Webster<\/a>:<\/p>\n

I couldn’t get my SwiftUI view to expand to fill up the entire superview that the NSHostingView<\/code> was being added to.<\/p>

[…]<\/p>

The next thing I came across was a property on NSHostingView<\/code> called sizingOptions<\/code>, which is described in the documentation as “The options for how the hosting view creates and updates constraints based on the size of its SwiftUI content.” Well that sounds promising! The default setting is all three options, [.minSize, .intrinsicContentSize, .maxSize]<\/code>, so I tried setting it to just [.minSize]<\/code> and lo and behold, it worked! The Spacer was now growing to take up the whole height of the superview! (setting [.minSize, .maxSize]<\/code> also worked)<\/p>

But, there’s just one problem… this property was introduced in macOS 13 and I’m still targeting macOS 12. 😭 But, after seeing this property and how it works, I think <\/em>I now understand what was going on with the size proposals earlier. I believe what NSHostingView<\/code> does is to probe its rootView once each so it can set up constraints for a minimum size, intrinsic content size, and maximum size. […] So what I need to do is basically reimplement what the sizingOptions<\/code> property is doing, which is to ignore the intrinsic content size of the SwiftUI view.<\/p><\/blockquote>\n\n

Previously:<\/p>\n