some Widget methods make sense to be redesigned as events since they share a lot in common with how they're passed on. events must be transparent to container widgets except when the containers actually want them, as opposed to requiring a new definition for each one that feasibly could be passed
some
Widget
methods make sense to be redesigned as events since they share a lot in common with how they're passed on. events must be transparent to container widgets except when the containers actually want them, as opposed to requiring a new definition for each one that feasibly could be passed