Closed actionless closed 8 years ago
no, as i stated in the commit message, i just need to know mute state and volume from the outside of the widget
So basically pulseaudio.lua should be a separate module apart from the widget itself, in order to do this cleanly. But I guess, since the change is really marginal, it wouldn't really hurt.
thanks!
Why do you want to let the widget expose pulse? Can you explain your use case? Seems to me, that would be only needed to move logic into your configuration file, which I personally would discourage.
Thx for your contribution.