Brian, great as always. This particular code would be perfect to make a corresponding video where you convert this code to use generics. I think with this particular use case, converting it would go along way to helping generics “sink in”
Well, in iOS 15 you can just use .refreshable(action:) List modifier but there's two things to consider: 1. your app should make use of async await so you can pass a closure with await statement to the action: parameter so the refresh control would know when to end refreshing. 2. this is not supported in iOS 14 and earlier and that's why I'm here watching this video 😁
I have two questions: - It doesn't seem to work without the NavigationView inside the GeometryReader. Why is that? I already have a root NavigationView elsewhere. - Does this support programmatic refresh?
Shipping swiftui with scrollview, which doesn't have a pull to refresh functionality is like having a car without an engine. Apple being a hot garbage once again.
Thank you! Waiting for the live stream
Brian, great as always. This particular code would be perfect to make a corresponding video where you convert this code to use generics. I think with this particular use case, converting it would go along way to helping generics “sink in”
Hello. So amazing. Which MacBook you have ?
crazy that we have to write so much code for a simple pull to refresh functionality
Well, in iOS 15 you can just use .refreshable(action:) List modifier but there's two things to consider:
1. your app should make use of async await so you can pass a closure with await statement to the action: parameter so the refresh control would know when to end refreshing.
2. this is not supported in iOS 14 and earlier and that's why I'm here watching this video 😁
@@AhmdIsmail 3. and .refreshable can't be customized for voiceover users, you hear "rose" during refresh.
Do you mind explain how does it work with async data? Sorry the reason I ask is because I got an issue with Pull To Refresh in Large Title
I have two questions:
- It doesn't seem to work without the NavigationView inside the GeometryReader. Why is that? I already have a root NavigationView elsewhere.
- Does this support programmatic refresh?
Shipping swiftui with scrollview, which doesn't have a pull to refresh functionality is like having a car without an engine. Apple being a hot garbage once again.
and if I don't need the list as a data display, your frame won't work correctly
This only works if data is synchronized....
How do you launch the second UI ?