@MoAlyousef this is quite the maneuver. But with the additional reference counting, record keeping, and maintenance complexity, is it still a better approach than the one used here? Even with the introduction of additional trait macros (such as impl_widget_ext_via, impl_widget_base_via, etc), I can't help but think that embedding a widget is a cleaner and more scalable approach.

Your example has the advantage of being able to properly handle events via the added widget instead of via the tree's callback method.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.