> 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
Well I can honestly say mine isn't working that way at all - I have an empty MC, nested into a scaled MC, this is contained within a holder mc. This swf is loaded into a container MC. localToGlobal gives the correct coords for the 'unscaled' mc's. container_mc.holder_mc.scaler_mc.point_mc The code which works out the point locations is in the scope of holder_mc. But as holder isn't scaled and loaded in at 0,0 it shouldn't make a blind bit of difference. If I want to get the 'real' stage coord for point_mc then I have to apply a scaler factor from it's _parent. When I found this out It confused the hell out of me as localToGlobal had never worked like that before - I just assumed I'd never used it with anything scaled by hand before and wrote that off as the reason. Now if what you're saying is true then it gets even more confusing. M _______________________________________________ [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
