'SwiftUI GeometryReader does not layout custom subviews in center
I have a custom view:
struct ImageContent: View {
var body: some View {
Image("smile")
.resizable()
.scaledToFit()
}
}
Which is being placed into another view with a GeometryReader:
var body: some View {
GeometryReader { geometry in
ImageContent()
//Image("smile").resizable().scaledToFit()
}
}
The problem is, the ImageContent view is not centered on the screen, it is being placed on the top, however, by removing the ImageContent subview and directly adding the view's content into the geometry reader will fix the issue (see picture).
Also, removing the GeometryReader can fix the issue as well.
I need the subview because I will be implementing some additional logic, and also need the GeometryReader because there is a gesture added to the Image that uses it.
Any idea?
Solution 1:[1]
I'm not sure why this is happening but you can use what others have suggested, or use the midX and midY from GeometryProxy's frame. Like the following:
var body: some View {
GeometryReader { geometry in
ImageContent()
.position(x: geometry.frame(in: .local).midX, y: geometry.frame(in: .local).midY)
}
}
Solution 2:[2]
You can use the GeometryProxy value passed inside your GeometryReader body.
struct ContentView: View {
var body: some View {
GeometryReader { geometry in
ImageContent()
.position(x: geometry.size.width / 2, y: geometry.size.height / 2)
}
}
}
This will define the exact position based on value provided.
Solution 3:[3]
I just ran into the same problem and I don't like the solution of setting the position manually because it complicates the process of automatically generating layout. For me the problem persists even after wrapping my content in a VStack. However, if you wrap the content in a VStack AND also manually set its frame - everything works as expected:
var body: some View {
GeometryReader { geometry in
VStack {
ImageContent()
}
.frame(width: geometry.size.width, height: geometry.size.height)
}
}
I think this issue pops up because GeometryReader's internal layout acts like a ZStack and it needs more information.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | |
| Solution 2 | richrad |
| Solution 3 | shim |

