Indeed. I meant a random / regular user doing that "for the sake of it". Me, I go with Update=1000 and UpdateDivider=-1 on anything I don't need to update more than once (since Update=-1 has other unwanted side effects, which I can't recall at this time but I noticed them in some cases) - the same principle as DynamicVariables=1 only when needed. I'm pretty sure I'm missing something too, since I don't know the ins and outs of the plugin code yet.While it doesn't matter a bit with this plugin, or any other plugin that has no independent action without being triggered, if you really want to do something "just for the sake of it", you can set Disabled=1 on the measure and it works just fine. The plugin will still set the value of the measure to what you enter, and I see no point at all in any MeasureName=#CURRENTSECTION# on the measure. I'm missing something.
Yep, that's what I meant with "it won't work" earlier - sorry about the scarce info then.Oh I see. So MeasureName=#CURRENTSECTION# will cause the measure to "retain" the value set by entering text. Otherwise, it will be lost after the actions are taken.
Statistics: Posted by Yincognito — 55 minutes ago