A problem with Buttons

[Gullyking]

I've used MMF2 for a long while now. Suddenly, when I started a new project, I'm having a problem with the darn buttons. I've set the buttons on my main menu to have 'behaviors' whereas, when clicked, they play a sample file and then of course they do whatever it is they do. The problem I'm having is that as soon as the application jumps to the frame with the said buttons, you hear the sound of the buttons being automatically pressed. Even though, I have them all set to 'disable at start'. One button, that labeled "exit" closes out the program, so when the frame starts, and the button for some reason automatically presses, it immediately closes. What could be causing this problem.

By the way, I've got it set in the behaviors so that the buttons event (SE and action) takes place 'once when loops'. Thereby, in theory, stopping the buttons from repeating SE and/or action, a lesson I learned a long while ago.

Anyway, let me know if you've heard of this before. It's irritating.

[LB]

How are you detecting when the button is pressed in the behaviors? Remember that behaviors are just events that get added to the end of the frame's events, the button objects don't 'run' the behaviors when they get pressed (how would they even know you wanted that to happen?)

[Gullyking]

Thanks, I wasn't really aware the order in which behaviors are calculated. That's good info.

As far as the behaviors I have, they are set up in each button like this in the behavior event editor (I'll use the start new game button as example):

If Mouse in over an object 'button' then play SE1
If user clicks button then play SE2, jump to frame 'New Game Setup'

What I don't get is the fact that the buttons are set on 'disabled at start' in the properties. Yet, I can hear them making the sound effects as if they are being clicked on, causing them to perform the action before the frame starts. It's quite odd. But using your reply as a basis, and given this new information, maybe it's best that I don't control the click of buttons through behaviors and just use the Frame Event Editor instead.

[Emerald]

I don't know if this relates at all to your problem, but one thing that drove me insane (the reason I created this account, actually) was that my buttons were being clicked for seemingly no reason when I pressed the spacebar.

It turned out that it's default windows behaviour to click a highlighted button when you press space (which is why it never showed up in my code, to my extreme frustration).
Is it possible there's something similar going on with you (i.e. outside influences acting on the buttons)?

[Gullyking]

That's possible, Emerald. I do have one frame where you must press 'spacebar' to continue. This jumps to a frame where some buttons are located. I'll look into that angle, as well. Thanks.

[LB]

Even if a button is disabled, the mouse can still be over it, thus it can still play the sound. Also, if you're using button click instead of button press, then they can always click on the button while it is disabled, too. If you happened to click on something right before going to the frame with the buttons, you may have clicked on the button anyway.

[Gullyking]

I just fixed this problem by removing the actions from the behaviors to the frame event editor. I don't see a 'button pressed' condition. . .Only 'button clicked'.

And you're right about the SE. You have to actually, set the condition up so that its:

IF button is enabled, IF button is clicked, once every loop = actions

I'll need to fix that. Funny, I learned that a while back and it didn't stick in my head for some reason.

[LB]

No, if you're using the button object, it should not allow clicking while it is disabled. I think there is something else going on here. Could you upload an example MFA of the glitch you fixed?

[Gullyking]

Well, I fixed it. So it's not really an issue anymore. I'll still try to make an example of how I set it up the first time, so you can see. Gimme a few hours, as I'm fixin to eat.