Avoiding unnecessary events and infinite loop in “coupled” JSliders?

Question

I have a GUI that is issuing commands to a web server based on slider values. Some of these sliders are \"coupled\" on the web server, so changing one of them may also chang

Answer 1

One author calls this problem fibrillation. This discussion suggests a shared model, in addition to the flag approach suggested by @Pyrolistical.

Answer 2

The standard model used in .Net WPF is to fire an event only if value of the property has changed! In your case it is setValue() method.

Answer 3

After struggling with this for a while and going into a mess with various booleans, I found that the solution was to simply add a check for hasFocus and respond accordingly.

• If a field did NOT have focus, then it would allow an update to itself, but wouldn't trigger updates to any other field.

• If a field DID have focus, then it would trigger changes to other fields.

This way, only the focused field can trigger any change and there is no infinite loop. The code is readable and simple, now, and the logic is easy to follow and update.

Answer 4

add an enabled flag to the listeners and disable them before manually setting the value

I wouldn't add and remove listeners as that just triggers more listeners!