Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the only ZStack one state for indicator, instead of removing that indicator view from hierarchy #42

Merged
merged 2 commits into from
Nov 2, 2019

Conversation

dreampiggy
Copy link
Collaborator

Fix for annoying bugs because the fact:

when writting the if else code with a Binding object, it will query the WebImage.body again.

This means, another new WebImage struct will be created, and receive a ImageManger.load (ImageManger is a class, which means they share the same state !). So the state mass up.

Using ZStack without changes will not cause the WebImage to be re-generaetd. This is the simplest solution.

@dreampiggy dreampiggy added the fix label Nov 2, 2019
@dreampiggy dreampiggy merged commit e8bb254 into master Nov 2, 2019
@dreampiggy dreampiggy deleted the fix_new_solution_for_indicator branch November 2, 2019 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant