Why would you even try to refresh the Mic skin if you're already activating it in the first place (which, assuming it was previously deactivated, does more or less the same thing)? Also, why would you even try to refresh the app (aka the whole Rainmeter and all active skins, plus rescanning the skins folder) if you only need the Mic skin to be "refreshed"?
Lastly, if I recall correctly, I suppose the skin made for the Mic is one of the many variants in this thread?
https://forum.rainmeter.net/viewtopic.php?t=38135
Now, it's been a long time since then and I probably forgot most of the things there, but it would have helped if you indicated which variant it is, or if you remade it yourself in a different way. As far as I remember, the PS variants didn't need refreshing, only AudioLevel ones, even though the PS ones had other drawbacks.
P.S. The subject has been investigated thoroughly (by you as well) in that thread, so I won't touch again whether detecting if the Mic is connected in your code above is the best way, but if all you need is a refresh and there's a way to stop whatever that skin is doing when the Mic is disconnected (for performance reasons or similar), you could simply hide and show that skin instead of deactivating and activating it, and refresh it from the main skin when needed. That would avoid a refresh loop entirely since the Mic skin would, in theory, always be active (or, at least, once the main skin is loaded, if you add the corresponding bang in the OnRefreshAction of the main skin, and add the opposite in its OnCloseAction).
Lastly, if I recall correctly, I suppose the skin made for the Mic is one of the many variants in this thread?
https://forum.rainmeter.net/viewtopic.php?t=38135
Now, it's been a long time since then and I probably forgot most of the things there, but it would have helped if you indicated which variant it is, or if you remade it yourself in a different way. As far as I remember, the PS variants didn't need refreshing, only AudioLevel ones, even though the PS ones had other drawbacks.
P.S. The subject has been investigated thoroughly (by you as well) in that thread, so I won't touch again whether detecting if the Mic is connected in your code above is the best way, but if all you need is a refresh and there's a way to stop whatever that skin is doing when the Mic is disconnected (for performance reasons or similar), you could simply hide and show that skin instead of deactivating and activating it, and refresh it from the main skin when needed. That would avoid a refresh loop entirely since the Mic skin would, in theory, always be active (or, at least, once the main skin is loaded, if you add the corresponding bang in the OnRefreshAction of the main skin, and add the opposite in its OnCloseAction).
Statistics: Posted by Yincognito — Yesterday, 11:42 pm