Monitor Name Bug
Posted: 08 Mar 2017 17:08
This will take 5 minutes for you to verify. Please help.
I stumbled across this gem while trying to troubleshoot another bug related to the default switch initialization when a template is loaded. That bug first:
1. Load the template in the editor
2. Connect to Lemur
3. Monitor1 shows that firstof(x) is 0, (rather than the monitor default of 120.350) indicating that somehow, this switch has been 'activated', since the script is triggered on Switch1.x 'up' I placed a ctlout() in that script and it IS being sent when the template loads. That's how this started...
4. Monitor2 shows that array1(firstof(x) is 0, which is wrong, since array1 = {'a','b','c','d'}
5. The buttons and monitors work properly otherwise.
That's part1. Can anyone explain this? Why is that script even executed? This DOES NOT happen with pads.
1. Disconnect the editor from the Lemur
2. Change the name of Monitor1 to foo, and Monitor2 to bar
3. In the onPress script, change the names of the monitors accordingly
4. Reconnect the editor to the Lemur
Both monitors now display their default values, 120.350
An anyone explain to me WTF the names of the monitors have to do with how they work??????????????????
For extra credit, change the default values of the two monitors to strings, ie '120.350'
Now they stop updating when the switches are pressed.
I stumbled across this gem while trying to troubleshoot another bug related to the default switch initialization when a template is loaded. That bug first:
1. Load the template in the editor
2. Connect to Lemur
3. Monitor1 shows that firstof(x) is 0, (rather than the monitor default of 120.350) indicating that somehow, this switch has been 'activated', since the script is triggered on Switch1.x 'up' I placed a ctlout() in that script and it IS being sent when the template loads. That's how this started...
4. Monitor2 shows that array1(firstof(x) is 0, which is wrong, since array1 = {'a','b','c','d'}
5. The buttons and monitors work properly otherwise.
That's part1. Can anyone explain this? Why is that script even executed? This DOES NOT happen with pads.
1. Disconnect the editor from the Lemur
2. Change the name of Monitor1 to foo, and Monitor2 to bar
3. In the onPress script, change the names of the monitors accordingly
4. Reconnect the editor to the Lemur
Both monitors now display their default values, 120.350
An anyone explain to me WTF the names of the monitors have to do with how they work??????????????????
For extra credit, change the default values of the two monitors to strings, ie '120.350'
Now they stop updating when the switches are pressed.