tink_widget_handler library

Classes

ChildWidget
Some widgets have a single child and hence need only the property name to that child whilst others have a list of children and need a name to that list hence either acts as a unifying type to achieve both
TinkRebuildScreen
Many widgets are stateless but Hypi provides the ability to update their attributes When that happens, we must rebuild the screen for the changed attributes to show up If your widget handler is stateful just call setState locally, no need for a global rebuild unless it affects other parts of the UI It is in effect the same as setState in a stateful widget but does not incur any overhead unless the widget's attribute actually changes
TinkWidgetRuntimeContext