From the icon docs:
1) The stack of the object's behavior (if applicable)
2) The stack of the owner of the object's behavior (if applicable)
...
n) The stack of the object's stack's behavior (if applicable)
A) The object's stack
B) The object's stack's mainstack (if a substack)
C) The object's stack's mainstacks substacks
D) The list of open stacks, in order they were loaded
It occurs to me that the stackFiles should come between C and D
resolving objects by ID
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, LCMark
resolving objects by ID
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/
Re: resolving objects by ID
I think the problem with doing that would be all the stacks in the stackfiles would have to be loaded in order to do a search.
At the moment, the stackfiles is only searched when resolving a stack name - and it only loads the stack referenced by an entry if the name matches.
i.e. if stackfiles contains foobar mapping to myfoobarstack.livecode then when resolving 'stack foobar', if "foobar" isn't already in memory it will load myfoobarstack.livecode as it.
At the moment, the stackfiles is only searched when resolving a stack name - and it only loads the stack referenced by an entry if the name matches.
i.e. if stackfiles contains foobar mapping to myfoobarstack.livecode then when resolving 'stack foobar', if "foobar" isn't already in memory it will load myfoobarstack.livecode as it.
Re: resolving objects by ID
Hmm... that's a good point...
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/