Get Layer bug :)

[Patrick]

Hey Yves, I found a bug.

Here is how to simulate it;
-Rename "Global Value A" to "Layer"
-Add an active object to the frame.
-Compare 2 values "If Layer-1<>Layer('Active Object')"

And voila, you got the bug. It gives a syntax error.
Now, to solve this, rename the global value "Layer" to "Layer2" or "LayerWhatever", and its fixed.

What i think is that it conflicts with the "Layer" part of the get layer feature "Layer('Active Object')".

[Joshtek]

Be careful with global value/string names as MMF2 won't complain about potential conflicts.

[Patrick]

huh? like?

[Nifflas]

Like the conflict you just mentioned. I don't see it as a bug really. In any programming language, you must avoid to give variables and functions names that the programming language already uses.

[Patrick]

Okey. but.. MMF has always been different than a programming language. You don't have to define variables, and so on... its just not comparable.
What im doing is following the logic of MMF, and according to that logic this should not be possible.

But i agree you should watch for duplicate names <img src="/center/images/graemlins/wink.gif" alt="" />

[the_raven]

But MMF is still a programming language and as such follows the rules of one.
And so must you.How should MMF know the differences between two things that
are both called 'layer'? It would have to 'look' closer and check if it's a variable
or an active object or a real layer or an active picture or a string [...].
You see this would take quite some tim and your application would slow down.

I hope I could clear things up for you <img src="/center/images/graemlins/smile.gif" alt="" />

[Patrick]

You are missing the point.

1. MMF is not a programming language in my opinion. Its a multimedia creation tool. Flash has "Action Script" action script IS a language, however that doesn't make Flash one.
Btw, go check: http://en.wikipedia.org/wiki/Programming_language

2. "Layer" and "Layer('Active')" are DIFFERENT variables ACCORDING to the LOGIC OF MMF, and so according to my logic.
In a programming language or MMF you have classes and objects which are practicly the same. These objects can contain the same variables as elsewhere in the application without being affected by that because they are bound to their object.

Sooo... if your still not getting it:
A is not AA

I agree with you when you say Layer and Layer conflict. but dont say Layer('Active') is the same as Layer. Cause its not. And thats working troughout whole MMF except on the Global Values. Which i think is a bug.

Please lock this topic...

[Joshtek]

[]Please lock this topic... [/]
Okay.