Architectural considerations for persistence relative to device settings
I'm probably missing something relatively obvious here, but, here goes....
I'm writing an application. In this application, I set the sound to be muted. Now, this mute persists through a power cycle. No issues there. However, I would like my application to know through a 'getMuted', if it existed, if we're muted, and update the appropriate visual controls.
There isn't really a 'getMuted'. This isn't too big of a deal, I know a workaround.
However, what concerns me, is the 'setMuted' function in AudioOutputPortImpl.java function. It sets the 'muted' value on the class-load to be 'false'. Which is fine and dandy, but how does it really know what the underlying native implementation really has as a value?