|

global startDrag problem

View: New views

5 Messages — Rating Filter: Alert me

	global startDrag problem by Bruno Zanchet :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 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
	Re: global startDrag problem by Julien De Luca-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 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
	Re: global startDrag problem by Bruno Zanchet :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 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
	Re: global startDrag problem by Julien De Luca-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 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... Julien De Luca - Parallèle Studio - Coopaname contact@... - 01 43 63 54 96 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
	Re: global startDrag problem by Bruno Zanchet :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Yeah, I agree. It's a static button, really. Could it be the cause? Let me show you the code: http://pastie.caboo.se/196236 <- this is working correctly, compiled in Adobe Flash (and not compiles in mtasc.). Using _global before startDrag, the code compiles (but doesn't work as expected) in mtasc http://pastie.caboo.se/196240 <- this compile, but doesn't work (curious: doing track.startDrag(true) the track becomes dragable - but not the progressTracker. Is this because "track" is a movie clip, while "progressTracker" is a button?) Bruno On Tue, May 13, 2008 at 12:40 PM, Julien De Luca <jd@...> wrote: 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... Julien De Luca - Parallèle Studio - Coopaname contact@... - 01 43 63 54 96 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 -- MTASC : no more coffee break while compiling