William F Pokorny <ano### [at] anonymousorg> wrote:

> Tried a few things quickly and v3.8 behavior I think OK. Test scene below:

Yeah, I don't know.
It seems like these things happen only sometimes, and in hard-to replicate
manners.

For instance, I just did a macro call on a macro that returns a 2 element array.
I got the ole' can't assign an unidentified something or other to Lvalue...

The macro has 2 lines.
#local Result = array {Val1, Val2};

Result

But somehow it thinks Result hasn't been defined.

So I deleted the #local and the Result, and just left the array.
Works fine now.

I don't get it.

Post a reply to this message