bluerobotics
Custom data-lake variables do not connect with Input Widgets
Bug description
#1752 introduced persistent custom variables in the data-lake. Connecting a numerical one to a joystick input or compound variable works fine, but when connecting a numerical or boolean one to an Input Widget there is no actual link to the underlying variable - changes to the variable are not reflected in the widget, and changes in the widget (while linked to other Input widgets with the same connected variable) are not reflected in the data lake.
Steps to reproduce
- Create a numerical custom variable in the data lake
- Create a new Input Widget (e.g. toggle-switch)
- Link it to the new variable
- Try toggling it, nothing changes in the data-lake display
Primary pain point(s)
The data-lake is supposed to be a unifying source of data, but that only works if the things it contains can be consistently connected to its input and output sources. Having a special variable type that doesn't connect to Input Widgets makes both systems seem less reliable/useful.
Additional context
Discovered while documenting.
Prerequisites
- [x] I have checked to make sure that a similar request has not already been filed or fixed.
Yup. This input-widgets implementation is behind on a lot of stuff. We should give it some care soon.
I can't replicate the issue on master, so marking as completed. Not sure if anything relevant has changed, or if it was a temporary problem with my setup or something 🤷♂️
Not sure what changed, but @rafaellehmkuhl noticed something similar to this was happening in a test, and I've just confirmed I'm experiencing it in v1.17.0-beta.9, so reopening.