Example : A dismissed Slidable widget is still part of the tree.

[giorgio79]

Hello,

Fixed the example so it works with the latest Flutter :)

I am noticing that the Slideable widget when dismissed emits a small error. Please see video. Any tips how to make this issue go away? :

dismissed.widget.still.part.of.the.tree.error.webm

(https://github.com/wwwdata/implicitly_animated_reorderable_list/assets/283347/ee9b58ed-46bf-42a1-92cd-abfbcbb67af7)

The recommended solution by Stackoverflow is to use UniqueKey instead of ValueKey https://stackoverflow.com/questions/55792521/how-to-fix-a-dismissed-dismissible-widget-is-still-part-of-the-tree-error-in

When switch to that, I am getting a small flicker in animation, as both Dismissible and AnimatedList is doing some animation.

double.animation.webm

======== Exception caught by widgets library =======================================================
The following assertion was thrown building SlidableDismissal(state: _SlidableDismissalState#c7a52(ticker inactive)):
A dismissed Slidable widget is still part of the tree.


Make sure to implement the onDismissed handle of the ActionPane and to immediately remove the Slidable widget from the application once that handler has fired.

[giorgio79]

Stackoverflow to the rescue!!!!
https://stackoverflow.com/questions/45919197/flutter-dismissible-insists-list-item-must-be-removed-from-tree
need to use confirmDismiss instead of onDismiss...

Testing the proposal right now

[giorgio79]

Still not perfect, but this one hopefully flutter/flutter#29844

[wwwdata]

So what about the suggestion to set removeDuration to zero and work with this confirmDismiss callback?

[giorgio79]

Yes, tried that. For some reason I still see the flicker in the Implicitly Animated widget. I tested going back to simple AnimatedList and no flicker there. Probably gonna go with AnimatedList for now.

[UngNhoThach]

tks bro so much

[makoConstruct]

It seems like this is partly due to an async yield happening in the didUpdateWidget, meaning the animated list doesn't actually update on the same frame as the dismissible is removed (happens on the frame after). Investigating.

[makoConstruct]

It seems like there's no way to block on a future in dart, so fixing this would require removing the MyersDiff call (MyersDiff doesn't allow users to run the diff algorithm synchronously, that method is private)

didUpdateWidget/its caller is synchronous, so if you await anything, the awaited code (myersdiff) runs after the widget tree is built, so the dismissed item will never be removed in time. (though it seems like it actually does sometimes, for reasons I can't explain and which definitely aren't reliable)