This content has been marked as final. Show 8 replies
I can't remember which version of Flash had the bug but the Limit coordinates were actually messed up between documentation and actual methodology. This has been address in CS3 and Flash Player 9 so perhaps it's an issue of this. Check the documentation in CS3's AS2 dictionary just to make sure.
Thanks! Glad to hear that there was a bug somewhere. I think I've figured out where the bug was, instead of being like the documentation of l,t,r,b it is b,r,t,l when inputting the coordinates, but the problem I'm experiencing is that it ignores the left limit, and automatically allows it to go back to 0 on the x coordinate system even if the limit is 100. It ignores it if I hard code it too and put in 100 as the limit within the startDrag function
I think I may just revert back to MX2004 for this project since it is due on Wednesday.
The MovieClip.startDrag method takes only 5 arguments. Remove the "this"
argument and it should work as documented.
yeah, I think i was reading the code hint thing wrong. I need to turn that off.
when it does startDrag(target,lockcenter,l,t,r,b) I was reading it as target of what is being dragged, so I was putting in 6 arguments, the this being what I wanted dragged.
Thank you so much, it's working now!
And if anybody from adobe reads this forum, your phone support is worthless. I was transferred 7 times, and finally ended up hanging up on the "technical" support after saying it was a customer service issue.
The code hint was probably giving you the signature for the global startDrag
function, which takes 6 arguments.
ouch .. what do we have here.. startDrag has different coding in AS3..
read the help files they are pretty good, and I will give u just a little code attached below to see how it works.. play with it for a while and you will see how things work ;]