The reason why I skipped detailed explanations is that, based on the contents and amount of questions, I would need to write pages and pages of replies and still not be certain you got it all. Might not be nice how I put it (sorry about that), but it's how it is - I don't lie to people just to sound good.
Yes, your variable + font color idea is good and it can work without conflicts, but you'd need to use escaping (and possibly nesting) to do it. When you set an option to a variable like you did, you're actually setting it to that variable's value, and not to the literal variable. Hence the additional detail that should have been done.
Instead of spending time explaining how that works, I proposed a simpler solution where you'd test 2 numerical values instead in an IfCondition. The result: you did get the IfMatch in the first line and what to test in the second line correctly, but got the || vs && wrong as per your goal:
So, the way it's supposed to work is:
1. Mic Disconnected = #White60#
2. Mic Connected and Active = #Green#
3. Mic Connected and Muted = #Red#
and you used an IfMatch instead of an IfCondition for the second line (despite advising otherwise, since IfMatch works with strings only, while IfCondition works with numbers only):
Code: Select all
IfMatch=[MicMute] || "#MicIconColor#"
See where I'm going with this, and why I'd need to write pages repeating myself at every step? Above, #MicIconColor# (which you should have named #MicConnected# to be more precise and logical) should be tested alongside MicMute (without square brackets, if you want to avoid adding DynamicVariables=1 to that section) exactly as your "supposed to work" breakdown, and then set FontColor accordingly in the meter. By the way, this IfCondition (not IfMatch) should be in the MicMute measure (replacing whatever other tests you have there, if any), because the said measure is the last compared to mDeviceName, meaning that by then both values being tested will be up to date.
Again, I don't have your setup and Line In to test, but like you said, if you get the Mic stuff right, you only need to replicate that for Line In, that's why I didn't cover the latter. Hopefully you'll be able to do that on your own, cause as much as I'd like to, can't help you there since I don't have a Line In to begin with, and there's just too much content in the thread to clearly and entirely understand how you want the skin to behave. It's tiring for me too to follow longer replies going from one thing to another repeatedly, you know... I already did that for the PS variants, it wasn't good cause the .dll is buggy, now I'll stick to essentials.
Regarding the need to refresh, I already mentioned the bug in AudioLevel in the PS thread, maybe it's related:
https://forum.rainmeter.net/viewtopic.php?t=40011
Hopefully I answered some of your questions above.
![Smiler :)](./images/smilies/ab.gif)