bugs in MX 2004?

[rapidcarbon]

I was creating a game in MX 2004, everything was fine, then just 5' later, everything stop working, even a button.

I have this button:_root.mcBttScreen.btOpen and the following code

_root.mcBttScreen.btOpen.onPress = function (){
_root.mcBttScreen.play();
}

they were wfine, then they stop, so I have to move the code inside the button and using on(press) to fix it

Anyone knows about this?

[rapidcarbon]

here is the link to the fla file, if anyone wants to take a look

http://www.tntt.org/vdh4/forums/flash/test.fla

[rapidcarbon]

anyone have this problem or just me?

[catbert303]

Hi,

the function for your close button isn't working because the button itself isn't created until several frames after the event handler is assigned to it.

You can fix this by editing the bottom screen clip in your movie. in this clip so in frame 1 of the button layer you have the open button as it was before and now also the close button, hidden off the edge of the stage.

next in frame 2 of this layer remove the blank keyframe and instead have a regular keyframe with both buttons hidden off the edge of the stage, finally in frame 15 have a keyframe where the close button is positioned where it is needed to be clickable.

[rapidcarbon]

thank you, I will try that, but I thought, when I invoke that function, the button already created

[Steve_w_V]

As for the name of the thread, there are many bugs in MX 04, which MM is working on.

[Thedeacon]

aye, I've been having so many problems in flash 2004 that I went back to the original mx. On a related note, does anyone know of a way to...er..splice in "normal" action scripting into flash 2004? and also the regular scroll bar that they *cough* seem to have forgotten to put in 2004's common library