Unexpected Variable hidding using include project action set variables before loading in action list

This might not be a bug...

When using an action list that has the same variable as a parameter as a variable passed to an included project via the "include Project" Action List, the "Set Variables Before Loading" modifies the variable in the Action List's variable space rather than the project's variable space.

From what I understand this might be just a consequence of the variable precedence rules, it is some what unexpected since setting the Action List's local variable value isn't propagated to the included project.

This might be just a caveat that I missed, but I've attached two files that demonstrate the behavior via the logging the value of the Variable "Variable".

Thanks

test12a.fbz6 (2.009 KB)test12b.fbz6 (1.411 KB)

Hi John

This is an unintended side effect of the variable precedence rules. The method we call to set the variables is the same one used everywhere else in the application, so it looks at action list parameters first.

This is really a case of don’t name your variables and action list parameters the same, something that holds true whether you are using the Included project action or not.

I will make a note to look at this again in the new year, as we will be making some rather hefty code changes to the action to support a new feature coming in FB7.