I'm trying to do a simple swap of a user variable from a wrapper script so that I don't have to change the orginal script. The user variable is a composite of four or 5 other variable so that I'm left with a very purpose specific output path that doesn't require any control logic. Anyway, the Set Variable doesn't allow the user to pull down any variable that is marked as a macro and it doesn't allow me to just type in any variable that I want, so I'm stuck. Now if it has be a non-macro because Final Builder has some kind of problem with macro within macro within macro, I'd understand. But... at the point that i'm swapping out the value i'm not using it as a macro variable, so if i could maybe turn off the macro flag while the swap is happening, I'd be happy.
Yes, FB (and AT) do not allow you to change the value of Macro variables. I think what you mean by swapping them would be fine to temporarily turn off Is Macro for the variables and then you can select them in the Set Variable action.
How do I temporarily change the flags on a variable? I was just putting it out there as a "wish". Remember this all has to be done from with in the script.
Yes, I understand that I would have to toggle it manually. But that is not practical. I can't toggle the value manual run a swap variables script then run the actually script I want to do. That's silly. I might as well type in the path variables every time I want to run the script.
I am requesting from finalbuilder the ability(the added feature) of being able to toggle the "is Macro" through an instruction, or the added feature of being able to edit an "is Macro" user variable.
Actually, for most purposes (ie referencing variables as %VariableName%) you can safely disable "is Macro" and just work with the variable current value, it will still recursively expand variable references inside the variable value. This will let you change the variable value, while probably still getting the behaviour you need.
No after some testing, it won't work. Those user variables must be macros because otherwise they are not being properly expanded when they are used to create the file paths.
In short I still need the ability(the added feature) of being able to toggle the "is Macro" through an instruction, or the added feature of being able to edit an "is Macro" user variable.