Problem editing MC in button state

[bobgodwin]

I've encountered a strange problem when editing the movieclip in button states. After going to the state, then going to frames, after returning to the main movie, the frame selector disappears and the movie gets a script error if I try to play it in the browser. Only if I stop the preloader will the movie play, but the frame selector's still gone. I've included a striped dpwn .fun file if someone would like to take a look. This has happened with several of my .fun files.

[Bob Hartzell]

I seem to be in slow mode these days. No one addressed this. I just downloaded it and will try to look into it in the next few days.

[bobgodwin]

Thanks. I've since remade the web site using shapes as movie clips instead of a movie clip in the button state and I don't get the errors any more. It MAY have something to do with the fact that I built the offending shapes as a seaperate .fun file then imported them into another .fun file. No idea really.

[bobgodwin]

Here's another test. Just creating a movieclipin the button state screwed up the interface.

[Bob Hartzell]

I looked at the second download. I don't understand what the problem is.

[bobgodwin]

On the frame with "button" on it, just try to edit the moveclip in the button over state and the frame selector disappears. It'll create a .swf that works, but I can't do much editting without being able to change frames. Tried to edit an older file from an old web site last night. Same thing happened. Something to do with the button states as a movieclip.

[docree]

I'm afraid that the bug you are having
is not a bug, but a limitation in flash.
Most flash buttons consist of states.
And each state has one frame.

I think Bob tries to keep us from doing
things that will crash flash.

If you want to make fancy animated buttons
you have to use go to and play/stop for
your movieclip.
DocRee

[bobgodwin]

But that's what the button is in the second test file, each state is a one frame moveclip. I used to make 'um all the time w/o this problem.

[Bob Hartzell]

Double click on the over state movie clip to gets properties. Then click on the frames button.

[bobgodwin]

That's not the problem. The frame selector for the main movie is the one that goes wacko.

[johnie]

Originally posted by docree
I'm afraid that the bug you are having
is not a bug, but a limitation in flash.
Most flash buttons consist of states.
And each state has one frame.

I think Bob tries to keep us from doing
things that will crash flash.

If you want to make fancy animated buttons
you have to use go to and play/stop for
your movieclip.
DocRee

I've gotton fancy animated buttons to work in the past... Although I did just Crash KM making a new one.

A work around, until the bug is corrected is to make your button then add a few frames with the button in it. Then assign your button states.

Attached are two files (One that crashes, the other that does not).

PS. That bug has been in there for quite some time (At least since 4.0).

[bobgodwin]

They both do the same thing for me. I don't have to edit anything at all, just going into the over state and going to frames causes the key frame selector to stop working. It's still there, but the slider bar is gone and the arrows no longer work. I'm stuck on the key frame I tried to edit the button on. Maybe I need to reinsall KM. Don't know. Flash version makes no difference. I can turn a shape INTO a movieclip and make that a button, but it's darn hard to line things up 'cause you can't see the original button tht way.

[Bob Hartzell]

Now I see the problem. It wasn't explained well. I will try to fix it today.

[Bob Hartzell]

I believe I fixed the problem and I sent a patch to Bob and Johnie. That bug has been there forever.

[bobgodwin]

That seems to have done it. Also, I see I'm no longer a junior member, but a full fledged member now. Cool.