« Return to Thread: global startDrag problem
Hmm, obviously this is not normal, i think you should try to find out why it does not work instead of using a workaround ;)is this a dynamically created clip ? In this case, you may have to make a container clip, it sometimes helps. If the clip is kind of empty, use an invisible rectangle to have a reactive zone behind.Also : Maybe the depth of the clip ? Try swapDepth in this case...Le 13 mai 08 à 16:37, Bruno Zanchet a écrit :Hm, interesting.Using _global, it compiles, but the object isn't dragable (same effect of movieClip.startDragging).--On Tue, May 13, 2008 at 11:28 AM, Julien De Luca <jd@...> wrote:
Did you try _global.startDrag() ?
Julien De Luca - Parallèle Studio - Coopaname
contact@... - 01 43 63 54 96
Le 13 mai 08 à 16:24, Bruno Zanchet a écrit :
--
Hello everybody,
Is there a way to use the global function "startDrag" with mstasc? I have a problem where calling movieClip.startDrag() isn't working (even with regular flash compiler), but calling the global function works. Does anybody noticed something like this? Any ideas?
Thank you,
Bruno
MTASC : no more coffee break while compiling
--
MTASC : no more coffee break while compiling
MTASC : no more coffee break while compiling
--
MTASC : no more coffee break while compiling
« Return to Thread: global startDrag problem
| Free embeddable forum powered by Nabble | Forum Help |