Protect dashboard from accidental changes while touch scrolling

I find I'm accidentally changing the values on 1x8 slider widgets while trying to scroll on a touch screen. I'm already trying to avoid touching the slider while scrolling but even then the slider will change. Anyone else deal with this?

I disable scrolling and force the use of the menu.
On another system I avoid the use of sliders and use drop downs with a range of various values instead. For example, for room temperature control I have a drop-down with temperature in 0.5 degree increments plus a low value for a room not in use setting.

Good suggestion but I'm finding the Dropdown doesn't display the input msg.payload like the Slider does. I have the Dropdown's options set as numbers (0-23, inc 1) and tried making sure msg.payload is an integer. The Dropdown node shows the input msg.payload but on the dashboard it doesn't. Some nodes like the Switch node have the option of displaying it's input or output but not the Dropdown. The Slider node doesn't have that option but it displays both input & output values.

It appears that I have to select the option "If msg arrives on input, pass through to output" for the Dropdown to display any input msg.payload but in my situation that creates a feedback loop.

That shouldn't be necessary. Can you share a test flow with a dropdown and some inject nodes that shows the problem?
Are you using the latest version of node-red-dashboard?

[{"id":"1e5886f5.b54501","type":"ui_dropdown","z":"4c195d90.05acd4","name":"","label":"","tooltip":"","place":"","group":"8c76602a.3ae5f","order":0,"width":"8","height":"1","passthru":false,"multiple":false,"options":[{"label":"","value":1,"type":"num"},{"label":"","value":2,"type":"num"},{"label":"","value":3,"type":"num"}],"payload":"","topic":"","x":300,"y":160,"wires":[["ae83212a.9a679"]]},{"id":"ae83212a.9a679","type":"debug","z":"4c195d90.05acd4","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":500,"y":160,"wires":[]},{"id":"f75998da.bfb058","type":"inject","z":"4c195d90.05acd4","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"1","payloadType":"num","x":90,"y":120,"wires":[["1e5886f5.b54501"]]},{"id":"fe764340.0a9d2","type":"inject","z":"4c195d90.05acd4","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"2","payloadType":"num","x":90,"y":160,"wires":[["1e5886f5.b54501"]]},{"id":"2a8c5629.91c9fa","type":"inject","z":"4c195d90.05acd4","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"3","payloadType":"num","x":90,"y":200,"wires":[["1e5886f5.b54501"]]},{"id":"8c76602a.3ae5f","type":"ui_group","name":"Test","tab":"bb4dc79a.2ffdf8","order":7,"disp":true,"width":"8","collapse":false},{"id":"bb4dc79a.2ffdf8","type":"ui_tab","name":"Sockets","icon":"dashboard","order":1,"disabled":false,"hidden":false}]

After creating this test flow, and confirming that it demonstrated my issue, I updated all my nodes and now it appears to function as I expected. I'm now using node-red-dashboard 2.28.2

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.