Is there anything on the roadmap that will eventually support specialized bindings in widget subclasses. Some use cases:
- A base class binding that I want to specialize in the subclass with a subclass of the base viewmodel
- An additional binding I want to make in the subclass widget that uses the base class’ bound viewmodel.
- An additional viewmodel that I want to bind in the child widget.
Right now we are working around some of these issues by not using the binding system and having functions in the widget base class “GetViewmodel” that are then specialized in the widget subclass, and doing bindings through blueprints rather than the binding interface, but this introduces a lot more boilerplate and complexity for designers.