beno - wrote:
On Sat, Nov 21, 2009 at 3:52 PM, Paul Andrews <[email protected]> wrote:
It's all good advice.
Attitude is important. Yours is good because it's not degrading.
It's may take you ages to track down these bugs, but a lesson will be
learned.
We programmers are gluttons for punishment ;)
Stipping back code until the problem goes away is a great technique.
Indeed it is!
I think I and others have already told you what the real problem is.
That may be true, but if that's the case, I've missed it. Here is
stripped-to-the-bone code:
package
{
import flash.display.MovieClip;
public class Main2 extends MovieClip
{
public function Main2():void
{
}
public function init():void {
leftHand();
}
public function leftHand():void
{
trace('left hand');
var mcHandInstance2:mcHand = new mcHand();
addChild(mcHandInstance2);
mcHandInstance2.x = 800;
mcHandInstance2.y = 200;
}
}
}
This is on the first frame of the only layer of the timeline:
var main:Main2 = new Main2();
addChild(main);
main.init();
stop();
"left hand" traces. No errors are thrown. Please tell, what have I missed?
If mcHand has a tween on the timeline for that MovieClip, there MUST be
a stop() command in actionscript at the end of the frames for the
mcMovieClip. Without that stop() command the timeline will loop.
Paul
TIA,
beno
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
