23 Mar
2015
23 Mar
'15
3:57 p.m.
On Mon, Mar 23, 2015 at 12:57:02PM +0100, Takashi Iwai wrote:
It's a good point. The notification via kctl can't follow the complete state changes since it's nothing but a notification telling "something changed". So, events like buttons that need the complete state change history, the current implementation isn't appropriate. For things like jacks, we usually care only about the final state, and the state change is much less frequent, so kctl notification works well.
I'd expect the buttons to be going through only as input devices, not as kcontrols at all.