Sure, but when you get down to actually designing the GUI, the mute/unmute control is going to be a single button. When that button is clicked it is going to toggle the state. Even if your library doesn't provide a toggleMute method, that is the logic that will be used in the button click handler.
Again, I agree with your overall point, not every boolean state semantically represents a toggle, but mute as it is used does represent a togglable state.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sure, but when you get down to actually designing the GUI, the mute/unmute control is going to be a single button. When that button is clicked it is going to toggle the state. Even if your library doesn't provide a
toggleMutemethod, that is the logic that will be used in the button click handler.Again, I agree with your overall point, not every boolean state semantically represents a toggle, but mute as it is used does represent a togglable state.