Forum Replies Created
Thanks, will keep my eye on the progress. Polling might be a temporary solution and is not that hard to implement.
Thanks for the amazing reply. Yes my application is partially intended for monitoring. Thus if I move the slider the other sliders on clients should change as well.
The ideal would be for the CHANGE event to be triggered for a user change as well, and announced to all clients, even if the value is not read from the PWM but from the stored values. However, my experience with firmata is null and not sure if that would be possible with standard firmata.
I know this might not be in your control and again thank you for your effort. How well does breakout work with custom firmata firmware? Your answer depends on how far I will go to make this work or look at another solution.
PS The websocket idea might not be viable as the clients might not be operating at the same time. I then might as well look at a Client-Server solution.
Would this be a valid feature request? Or would this require custom firmata firmware?
I also found a small bug in your example. The slider does not go back to 0 after changing it, but to 0.5 (0 for some reason becomes the next value when you drag it one step to the right). The solution can be found here:
Specifically the comment to the answer:
Actually, there’s a subtle difference in all this (I just ran into this myself). You should use “ui.value” to get the value in your slide event handler. That will give you the current value. You will get the previous value if you fetch it by asking the slider for its handle value (e.g. .slider(‘value’) or .slider(‘option’, ‘value’), etc.). This matters if you are trying to say dynamically update a label while the user is sliding the handle around. Summarizing: if you use ui.value to get the value in the slide event handler, you won’t need to use a stop event handler.