[FEATURE] OnChangeStringAction vs OnChangeNumberValue

[Yincognito]

This is related to this bug report here. For measures having different string and number values, you sometimes want the OnChangeAction to trigger only when one (and not when any) of those values changes. Example (related to the mentioned bug report, but can be extended to other measures having different number and string values):

Code: Select all

[MeasureWin7Audio]
Measure=Plugin
Plugin=Win7AudioPlugin
OnChangeAction=[!Refresh]

This provides the current / default output audio device name as its string value and that device's audio volume as its number value. You'd want the refresh bang to happen only when the device changes and not when you change or set the volume.

I know this can be achieved with an IfMatch / IfCondition as well, but it requires saving the previous value and if we have the OnChangeAction option, why not use it? Not sure about how to internally differentiate between strings and numbers since, if I'm not mistaken, I recall reading somewhere that everything is a string in Rainmeter, or regarding the naming convention for the "other choice", but that is up to the developers (maybe an additional option like OnChangeTarget being 0 for any value which would be the default, 1 for the numerical value and 2 for the string value, or something along these lines)...

UPDATE: Just realized that this can be easily achieved by using the string value of this measure in a subsequent String (or Calc and using the numerical value, if that value is the target) measure and moving the OnChangeAction option there, like:

Code: Select all

[MeasureWin7AudioString]
Measure=String
String=[MS_Win7Audio_Win7AudioDevice]
OnChangeAction=[!Refresh]
DynamicVariables=1

[deflore08]

I though to reach this by storing in variable and call comparing function. Really easy. )) Thanks.

[Yincognito]

I though to reach this by storing in variable and call comparing function. Really easy. )) Thanks.

Yeah, storing the previous value is one way to do it. I didn't realized I could do the test in a subsequent suited measure using the same OnChangeAction at the time of posting though, so the feature suggestion became pointless after having that second thought about it.