private function getPath( mc ):String {

var path: String = '';
var aParent = mc;

while( aParent.name != 'root1' )
{

    path = aParent.name +'.'+ path;  
    aParent = aParent.parent;

} 

path = aParent.name +'.'+ path; 
return path

    }

Is there a simplier way?

May i ask why you need the path of the clip?

Just curious

if your just trying to access a clip by instance name you could do:

containerObject.getChildByName("objectName")

but i am not sure i am understanding what you need exactly

though I suspect JLM wants to display the scope in some way thus needing it as a stinr... in which case, I can't think of a cleaner way to d it other than what J has suggested.

I realise that I am not up to speed with AS2/3 but, are you not replicating the AS1 _target property off the movieclip here?

In which case, why not use

private function getPath( mc ):String { return mc._target; }

scudsucker

no does not work i think ie

trace( this._target ) root._onScreenDebugTextfield.text = this._target;

well top one anyway.

As Arsis indicates I need the timeline scope as a string. Let me explain; if you have a complex structure it is usefull to be able to place code on a movie to check where it is, not so much for general use but when something is not working also allows you to directly access a movie from anywhere and can be a usefull when getting something working prior to doing the proper code. It used to be a usefull tool for helping debug. For instance I am loading in a movie based on flashvars and when it is there I want to be sure it is in the right structure and check when it is created etc..

I understand why this has all changed but I do not want the info for oop abuse I want this for debugging/checking assuptions, shame nothing like this is built in as my code seems rather a nasty last resort.

Non support for this sort of thing is going to really anoy any designers trying to hack out a prototype interactive, is Adobe pandering to the Java guys too much and forgetting the designers that code banners?

I can answer YES to that one. Adobe has kind of taken away some of our talents that we've built up over the years.

But I can totally understand the 'why' of JLM's post. I just don't have any answers.

Are there still any 12st members who are working directly with Adobe doing testing, research, or devolopment? It might pay to contact them and see if anymore light can be shed regarding the way developers seem to be losing this type of support?

As a collective (12st or otherwise), you would find that making a submission based on the above post(s) and similar examples and situations would have a better impact for the changes. I would suggest collaborating so that you all still can continue to use those "tools" and processes.

.. seriously, it would be worth getting together for?

No...

Bought the pro haxe and neko book yesterday, join me in learning haxe instead.