MegunoLink

When any control with a 'changed' message has its value changed by a message from the micro, it sends the 'changed' message to the micro - which is pointless as that message effectively just repeats the message the micro sent in the first place that changed the control.

'Changed' messages should only be sent when the control is changed by the user, not when the control is changed by the micro (eg effectively by Megunolink itself).

Not exactly harmful, but wastes comms bandwidth and micro comms buffer space and CPU cycles.

Especially wasteful when the micro is initializing many/all controls to a known state.

Related bug, but separate to this, is that Changed messages are NOT sent when control values are loaded from a file via "Load values from File".

That's a serious bug as it renders saving and loading of control values pointless if the micro is relying on Changed messages to inform it of changes to control values (instead of requesting the values).