https://xkcd.com/3167/
'They really shouldn't let those small cars drive in traffic. I worry I'm going to kill someone if I hit one! They should have to drive on the sidewalk, safely out of the way.'
Explain xkcd: https://www.explainxkcd.com/wiki/index.php/3167
https://xkcd.com/3167/
'They really shouldn't let those small cars drive in traffic. I worry I'm going to kill someone if I hit one! They should have to drive on the sidewalk, safely out of the way.'
Explain xkcd: https://www.explainxkcd.com/wiki/index.php/3167
Does anyone know of a way to use NavigationStack, to animate a push to a new screen. While also removing the current screen from the stack?
Alternatively you could remove the current screen after the animation completes. As long as that’s not animated.
Does anyone know of a way to use NavigationStack, to animate a push to a new screen. While also removing the current screen from the stack?
Alternatively you could remove the current screen after the animation completes. As long as that’s not animated.
Has anyone used these? Any tips? Any pitfalls to avoid?
I’ve already noticed DisclosureGroup has issues compiling with recursion.
#SwiftUI #Swift
I’m worried I’m over engineering mine using navigation destinations for values, and also loading “initial” columns on first appear (using isPresented navigation destinations).
#swift #iosDev
Javascript: "What's a bear?"
Java: "An actual bear or a bear factory?"
Go: "I'm worried because I implement Biteable"
Haskell: "Nothing in this room can harm me"
Rust: "So the next room is unsafe?"
C and C++: "Who cares? Just don't go into that room"
Javascript: "What's a bear?"
Java: "An actual bear or a bear factory?"
Go: "I'm worried because I implement Biteable"
Haskell: "Nothing in this room can harm me"
Rust: "So the next room is unsafe?"
C and C++: "Who cares? Just don't go into that room"
#DoctorWho
#WhoSky
#DoctorWho
#WhoSky