Posts

Post marked as solved
1 Replies
1.1k Views
I had the latest XCode 11 beta installed side by side with the XCode 11 GM (first), but was strictly using the GM at this point. Today, I decided to get rid of the beta for good and deleted it, but it seems to have taken all of the iOS 13 simulators with it. I've tried reinstalling GM 1 and 2, but neither action has brought back the simulators.When attempting to run my code on an iOS 13 simulator, I get "The iOS 13 simulator runtime is not available."Details: When I go to XCode > Preferences > Components, no iOS 13 simulator is listed:When I try to add an iOS simulator manually via XCode > Devices and Simulators, I get "The operation couldn't be completed. Invalid argument"
Posted
by onethread.
Last updated
.
Post not yet marked as solved
0 Replies
355 Views
It looks like spacers provide spacing dependant only on their parent view's context, so something likeVStack { ViewA() Spacer() ViewB() Spacer() ViewC() }will equally distribute spacing, but the following will not render equivalently. The "outer" spacer will push ViewBC down as far as possible, and then the spacer in ViewBC will do its thing (but usually will end up doing nothing because the outer spacer already took all the available spacing)VStack { ViewA() Spacer() ViewBC() }where ViewBC is defined asVStack{ ViewB() Spacer() ViewC() }Bundling into ViewBC can be useful in situations where components that are reused often. So what's the workaround? Is there a way to tell SwiftUI that I want ViewBC to consume more of the available space? Or is the idiomatic expecation to render all components at the same level?
Posted
by onethread.
Last updated
.