Bug in FMX2004
- Started
- Last post
- 10 Responses
- Bozilla
Ok, now if somebody would help me out and tell me if this is a bug or what I would appreciate it a lot. I've noticed strange behavior with stop() command and frames, especially when called several times. Let me show you what seems to be weird and obviously fooked up with Flash MX 2004 Pro.
download this FLA and just run it in Flash and look at the trace messages. You will understand what I'm talking about. Btw, this thing worked fine in Flash 6 and stop() was the stronger function than play(). Now it doesn't seem to be so. Very very strange. This is causing a lot of problems when I work on large projects and I'm just thinking seriously to return complete Studio MX 2004 and ask for my money back.
FLA file mentioned here:
http://www.designbyinfinity.com/…Cheers.
- pixelbreaker0
Bozilla,
I just tried it, it's fine for me in MX2004 Pro on PC, updated to 7.0.1
- Bozilla0
pixelbreaker..try clicking twice on teh button..it will break the stop() and go to the next frame....don't click only once. Click twice..you'll see it..
- contra0
Nowt wrong with it as far as I can see, it stops on 'testing' and doesn't go to the last frame.
- contra0
Use gotoAndStop then.
- Bozilla0
you can't my friend because gotoAndStop doesn't execute subclip contents only gotoAndPlay does
- mennik0
Put your framelabel 'testing' on the previous frame. One frame before the stop(); function.
Right now you're calling a play(); and stop(); function on the same frame, that's asking for trouble imo.
- Bozilla0
well that's the whole point...it worked before without any problems...in Flash 6, stop() was highest level command. So that means that nothing past through it. There are so many applications that this made possible, now in Flash 7 it doesn't work.
- MX_OnD0
it's not expected to work. If it did in FMX then BONUS. Still doesn't make it good practise. Also you have FMX2004 and have scripts on buttons???
use myButton_btn.onRelease = function() {
}
on the main timeline.....
dot syntax for the past 3 versions....
- Bozilla0
MX_onD, very nice from you to give advice about coding practice, however I know more then you think, so there's no need to try to express your great knowledge here. The example here was done in 5 sec and for sole purpose of showing that it doesn't work. And, btw, why exactly isn't that fla suppose to work? If you say gotoAndPlay a frame and put a stop in that frame it should stop regardless if you call that frame once or twice or three times.
- MX_OnD0
sorry Bozilla, I didn't mean to offend you.
I was just trying to help.
Anyway back to the issue at hand:
As was stated before telling the timeline to stop and start at the same time will result in confusion. That's why it can't be expected to work. As the capabilities rise so does the exactness that is required.