This repository has been archived by the owner on May 1, 2024. It is now read-only.
Replies: 1 comment 3 replies
-
@Jared-Aus the And as I said on the show, if you want another kind of LazyView, maybe one that supports an AcitivityIndicator, open an issue as a feature request and let's talk about it. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current marriage between TabView and LazyView seems somewhat broken to me. If the only requirement was for the initial tab or page to be not slowed down by the loading of other tab items, a simple IsLazyLoaded property might have been sufficient. By utilising LazyView and having the TabView implementation tied to BaseLazyView there is seemingly more power for developers, however that power is immediately taken away as there's no control over when the lazy views are loaded. If your second tab item takes 3 seconds to load and you want to use a custom LazyView implementation that starts life as an ActivityIndicator, the tab doesn't switch for 3 seconds as it's waiting for the lazy view to fully load. My guess is that's a bug in the implementation, but it could be intentional for all I know.
Wrapping the lazy view in a ContentView or nesting lazy views gets around the tight coupling, but then we're back to square one. A basic feature would ideally be simpler to use, or a more powerful one less rigid.
Beta Was this translation helpful? Give feedback.
All reactions