Could relate to the particularities of the plugin, yes - though it's a bit inconvenient given what's expected to happen in all the other parts of Rainmeter, including all the other plugins.The SetOption on DefaultValue is needed because UpdateMeasure doesn't really update the plugin in a sense of re-reading the options, this is because the NestedVariable on DefaultValue is not read as a nested variable, but it's literal value, so updating the variable won't affect the DefaultValue option as it's not really dynamic, so re-setting the DefaultValue and then updating the measure is needed so it actually reads the new value.
Not sure why is this, so in my mind a Reload command would help to make the plugin update the values that <should be> dynamic. Maybe making these options dynamic breaks the plugin or something, however in my mind this should not be the case, maybe is just a slip somewhere on the code and can be fixed easily. That's up to the author to tackle.
The DefaultValue (and all other options) should read it's value dynamically if DynamicVariables=1 imho.
By the way, I originally did NOT use the nested syntax for the variable in the DefaultValue option. So basically, even so, the the set option trick is needed to dynamically change the value of the measure and its DefaultValue option. If that works as per your advice, that is, still didn't get the chance to test it, but will do shortly.
Statistics: Posted by Yincognito — 56 minutes ago