I am fully aware of what the original poster was asking (I was also
interested in the technical question of internal name references when we
brought it up). And yes, it was a case of misreading - you don't care how
Director handles it - but this was fresh off the back of a few other posts
from
I don't know and I don't care...
Bit harsh, isn't it?
Is it just me or are people getting a bit short-tempered at the moment (no
names will be mentioned)? I
could just be reading stuff the wrong way but there are a few list regulars
who seem to have little patience with simple questions or
Hi all you gurus
Just wondering if you can tell me how field names are stored internally. I
have named two fields with the same name expecting them to receive identical
data from a list but only one actually receives it. I was wondering if it
was because they may be stored as an array and
I have named two fields with the same name expecting them to receive identical
data from a list but only one actually receives it.
Do you mean you have two field cast members with the same name? Or two
variables with the same name, holding data from a field?
If you have two cast members of
At 10:58 PM +0100 5/19/01, Alan Robinson wrote:
Hi all you gurus
Just wondering if you can tell me how field names are stored internally. I
have named two fields with the same name expecting them to receive identical
data from a list but only one actually receives it. I was wondering if it
was
Do you mean you have two field cast members with the same name? Or two
variables with the same name, holding data from a field?
If you have two cast members of the same name, Director will always use
the
first one. If you have them in different casts, you can differentiate them
by using the
