> actually, I'm not sure if localToGlobal does anything with
the scaling.
> I have the feeling it simply adds coordinates of parent
movieclips to
> the local ones..
I'm not sure what you're doing and how, but it *does* take
into consideration the whole movieclip matrix info -
rotation, scaling, skewing, etc. It's really the best way to
translate a position from one movieclip to another.
This may be the case if you've transformed it in code, but definitely
not the case if you've scaled something on the timeline.
That's strange, because I've just done that to test and it's definitely
working - even within a timeline tweening, and taking scaling, rotation and
skewing into account; it's properly reading an arbitray point on the
movieclip and moving a crosshair on the main stage to that same point
position.
Maybe I'm missing something big that you're having to deal with, but I have
no doubt localToGlobal works as designed.
- Zeh
_______________________________________________
[email protected]
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
