You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you want to add or remove gesture detection, it's intuitive to think that the following should all be equivalent:
Having a test in the handlers.
Having a test in the build function that decides whether to set the handlers.
Having a test in the build function that decides whether to have a GestureDetector at all.
Having a test in the build function that decides whether to have a GestureDetector at all, where the child of the GestureDetector is a KeyedSubtree with a new GlobalObjectKey(this).
The first two and the fourth are in fact equivalent (the second is slightly slower, the fourth slightly slower still), but the third is not. The third will cause all kinds of state to drop.
We should fix that. Until we do, we should document the heck out of it.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
abarth commentedon Feb 1, 2016
I'm pretty happy with the "state follows global keys" design we ended up with.
Reland "Compile libcxx and libcxxabi (flutter#190)" (flutter#193)
github-actions commentedon Aug 17, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.