[Needs Thinking] Consistency between InstrumentSettings and Swing after user input.

[jandejongh]

[AbstractInstrument] At the present time, user input on an [Swing] Instrument View typically results in an applicable "request" to the Instrument. If the request results in a change in Instrument Settings, the implementation of AbstractInstrument will report the new Instrument Settings to its listeners, and as a result the Instrument View Swing state will be updated.
However, some user interactions result in an immediate change in Swing components, and if the "request" did not result in different Instrument Settings, the component is not informed about it because AbstractInstrument only propagates changes to the Instrument Settings.
As a result, the Swing component is left in an inconsistent state.
A solution could be to inform AbstractInstrument that a specific listener wants ALL readings of the InstrumentSettings, instead of just the "deltas".