MDFastBinding
MDFastBinding copied to clipboard
Function nodes do not reset or show warning when changing its function owner to a different type
It is possible for a binding to try and call a function that doesn’t exist for its function owner type, by swapping its type to another after having already selected a function.
Steps to reproduce:
- Create a widget with an
Imageand aTextBlock, and ensure that both are exposed as variables - Create a binding with a
Read a Propertynode for theImage - Connect its output to a
Call a Functiondestination node, and set its function toSet Color and Opacity - Create another
Read a Propertynode for theTextBlock - Connect its output to replace the Function Owner parameter of the
Call a Functionnode - Observe that no errors are displayed, and that the blueprint saves/compiles without warning
- Add the widget to the HUD and run PIE
- Observe that the engine crashes, with a callstack implying that it tries to invoke
SImage::SetColorAndOpacityon theTextBlock