Matrix user forums

Hi

I have a problem importing a Macro that have the same variables names .
In V5 i could just click to use the same global variable name , but in V7
there is no option to do it .

These are global variables that i use in multiple macros and will not conflict

Is there any work around for this ? , i am stuck can't continue

Hello,

I've just tried this with two macros both using a global variable and the macros are both importing ok into a new program.

Are the macros your trying to import v5 exported macros? If so then can you load a project containing the macros in v7 and then export from v7.

Hopefully this will solve the problem for you.

Hi Benj

Thanks for your reply , i did not import in a new flowcode file , the variable name was already used .
Also the macro was exported using Flowcode 7 .

first I get a window saying that there is a variable conflict and to click yes to change the name
in the example below it's only 1 variable so it's not a big problem .

I managed to get around by renaming the variables , than after import changing all variables to the one's
i originally wanted and delete the new ones.

But in v5 it was much easy, there was a button to use the same variable name .

Hi

Is there a specific reason why Use Existing Variable button has been Removed in V7 ?

It seems that no one wants to answer my question and it's not a complicated one !

Hi,
Are the project global and the imported macro variables of the same type?
I would suspect that they are not, and that this is the reason that you are being forced to rename the imported one.
Hope that helps,
Leigh

Hi Leigh

OK so now I have an Answer to my question, Flowcode should Automatically use the same variable that is why the
button has been removed OK.


So No the variables are of the same type 100% sure , But i finally found what is causing this
if in the main program the variables have an Initial Value set , Flowcode will force you to rename
it that is why it was tricky to see the problem .

below I attache an fcfx file and a test macro try to import and see what happens than check the variables .

Thanks

Thanks for the further investigation and info.
I'll add this issue to our internal bug tracker.
Thanks,
Leigh