The DynamicVariables option itself is like an ON / OFF switch that allows a section to read the changed values of its options (which can contain variables too, as you already know).
What I did in the 2nd Button above was simply turn that switch ON in the section so it can read the changed path variable, update the section to apply, then turn back the said switch OFF and update the section again so the FileView parent can work normally with dynamic variables "disabled".
The only difference from the usual way of "permanently" hardcoding DynamicVariables to a certain value in a section, was that this time the said option was only "temporarily" changed so the variable could be seen, then changed back so the FileView parent could work properly again (obviously updating the measure after each change).
What I did in the 2nd Button above was simply turn that switch ON in the section so it can read the changed path variable, update the section to apply, then turn back the said switch OFF and update the section again so the FileView parent can work normally with dynamic variables "disabled".
The only difference from the usual way of "permanently" hardcoding DynamicVariables to a certain value in a section, was that this time the said option was only "temporarily" changed so the variable could be seen, then changed back so the FileView parent could work properly again (obviously updating the measure after each change).
Statistics: Posted by Yincognito — Yesterday, 4:23 pm