Win7Audio string not updating = confusion [solved]

[Mor3bane]

Thanks eclectic-tech.

As usual your awesome skill and artistry shine right through the issue/s.

[Mor3bane]

So with a lot of help, not only in this thread, but in others I participated in and learnt from over the past couple weeks - I now present what I feel is a decent Beta of what I hope to have in this kind of skin.

There are a couple features still on the books -

So without going overly into the workings, I'll just simply post it and see if anyone is curious about how it works, or if they find it reasonably intuitive.

I hope some people will find this useful and fun.

Audio Wizard_xx.04.rmskin

There are some caveats - system configs will differ as well as audio ability/functionality.
I found that going through windows 10 and exploring the different sound managers within it - this skin makes it easy to have 7.1 the switch to headphones/speaker in headphone socket for 2 channel output rather than more speakers of ch4 ch6 ch8.

I made this to easily change to lesser output settings for mp4 or avi that do not support 5.1 or 7.1.

[balala]

So without going overly into the workings, I'll just simply post it and see if anyone is curious about how it works, or if they find it reasonably intuitive.

Although this isn't a problem and the code works even so, I still believe that using the !ShowMeter / !HideMeter bangs instead of setting the Hidden option of the meter with !SetOption bang (IfMatchAction and IfNotMatchAction options of the [MeasureWinSevenAudio] measure), is a better choice. At least me personally definitely prefer this one.
But again: setting the Hidden option works same well.

[Mor3bane]

Although this isn't a problem and the code works even so, I still believe that using the !ShowMeter / !HideMeter bangs instead of setting the Hidden option of the meter with !SetOption bang (IfMatchAction and IfNotMatchAction options of the [MeasureWinSevenAudio] measure), is a better choice. At least me personally definitely prefer this one.
But again: setting the Hidden option works same well.

Yes that is so on average, however, to toggle regardless of state this way is better, as the logic remains clear even if a manual refresh takes place out of "sequence".

[balala]

Yes that is so on average, however, to toggle regardless of state this way is better, as the logic remains clear even if a manual refresh takes place out of "sequence".

I don't see why, but you know better. Maybe if something like [!SetOption "HeadsetPNG" "Hidden" "#SomeVariable#"] would be used, definitely has make more sense to use this technique, but why [!SetOption "HeadsetPNG" "Hidden" "0"] / [!SetOption "HeadsetPNG" "Hidden" "1"], with explicit values set for the Hidden option?

[Mor3bane]

I don't see why, but you know better. Maybe if something like [!SetOption "HeadsetPNG" "Hidden" "#SomeVariable#"] would be used, definitely has make more sense to use this technique, but why [!SetOption "HeadsetPNG" "Hidden" "0"] / [!SetOption "HeadsetPNG" "Hidden" "1"], with explicit values set for the Hidden option?

Wait are you looking at xx.04?

[balala]

Wait are you looking at xx.04?

Yes, I definitely do. I'm talking about the [MeasureWinSevenAudio] measure of xx.04.

[Mor3bane]

Like I said - it preserves the state through a refresh so the skin remains with intended behaviour of buttons being visible through internal updates when the sound device finishes from an output channel change.

[balala]

Like I said - it preserves the state through a refresh so the skin remains with intended behaviour of buttons being visible through internal updates when the sound device finishes from an output channel change.

No, not agree. The !Setoption bangs don't preserve nothing. The !WriteKeyValue bangs used into the same IfMatchaction and IfNotMatchAction options indeed do and they are alright, but the !SetOption don't preserve nothing.

[Mor3bane]

Well, to be clear, I did not disagree with your advice, only that the code I was using was intended as stated.

So now I have changed to Show/Hide Meter bangs in the [MeasureWinSevenAudio].

Of course the behaviour was not different.

So again, to be clear what was the issue with SetOption anyways? Simply too many juggling options? I cannot see any potential for performance being the reason. Nor does it affect the end user in any manner.