Hello :)
you can try
_root._lockroot = true ;
?
EKA+ :)
2007/2/17, Hans Wichman [EMAIL PROTECTED]:
So, any ideas anyone? This 'feature' kinda messes up the whole system atm
...
thanks in advance
JC
On 2/14/07, Hans Wichman [EMAIL PROTECTED] wrote:
Hi,
in an application I am working on, I was 'forced' to use _lockroot
(until
the architecture can be reevaluated:))).
So assume main loads sub into a path _root.sub and sub has _lockroot to
true.
If I trace _root from sub, it prints _level0.sub as it should.
However when I load sub for the second time (with different parameters),
_root stops pointing to _level0.sub and reverts back to _level0.
Even more strange, sub initializes some webservices and if i do:
trace 1:+_root
var myWS = new webservice
myWS.onSuccess = onSuccess
onSuccess = function () {
trace 2:+_root
}
It will print:
1:_level0.sub
2:_level0.sub
the first time sub is loaded, and
1:_level0.sub
2:_level0
the second time.
Has anyone seen this behavior before?
greetz
JC
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
