Targetting the top level of menu bars?

[rbb]

Hi,

I've got a menu bar with a few drop down sub-menus, which I can target fine. But the mast item on the top level of the menu bar, I want to be "exit", but it will have no sub-menu. How do I go about targetting items on the top level of the menu bar?

Thanks,

rbb.

[yorkeylady]

Still learning about this myself.
Here's my best guess.
myMenu is the instance name of the Menu Component, (Not the MenuBar which creates the drop down instances)

myMenu.onPress= function(){
  // insert your code here
}

[Jotun75]

Hi!

I have an undocumented solution to how to target the menubar items.

Goes like this.

myMenubar.addMenu("start")
myMenubar.addMenu("help")

ok now my menubar has to menuitems with no dropdown menu.

If you want to target an onPress on just the menubar item instead of having a dropdown menu on it, you do as this -->

The target to "start" is myMenubar.mbItem200
so simply assign

myMenubar.mbItem200.onPress(){
        //whatever action u want
}

Try to guess what this targets

myMenubar.mbItem201.onPress(){
      //whatever action u want
}

Yepp, it targets the "help" item.

So in short the menubar item is named from start to end mbItem200....mbItem20n.
Strange that MM dont have this in their docs, go figure.


I know my english aint good, sorry for that.

[pigpen]

I'm having trouble with the mbItem200 method you explained. Can you attach a fla example?

thanks.

[Jotun75]

Originally Posted by pigpen

I'm having trouble with the mbItem200 method you explained. Can you attach a fla example?

thanks.

here is the file

[pigpen]

Thanks! Very interesting. No event listeners needed. Thats why I couldn't get it to work using your method because I was added listeners by mistake. Makes sense now.

I'm curious. How did you find out about this mbItem? Yeah you would think MM would have this in thier docs.

[Jotun75]

I found it out by chance while debugging. I was curious about the structure and objects created at runtime, so when I did a closer look at the objects on the component in the debugger I discovered the pattern in the reference mbItem200,mbItem201,mbItem202 and so on matched my actual menubar items.

[pigpen]

Nice. That reminds me to use the debugger more often, especially when using these often under-documented components. Thanks again.^^

[chrispix]

Thanks for this! You saved me a ton of work. One correction to the syntax of your example:

myMenubar.mbItem200.onPress(){
        //whatever action u want
}
Try to guess what this targets :)
myMenubar.mbItem201.onPress(){
      //whatever action u want
}

should be

myMenubar.mbItem200.onPress = function() {
        //whatever action u want
}
Try to guess what this targets :)
myMenubar.mbItem201.onPress() = function() {
      //whatever action u want
}

[mcarey]

When I attempted this workaround, I got a compiler error if I did not include a level scope when targeting the menubar component.

So...

myMenubar.mbItem201.onPress() = function() { ...

produced this error:

There is no property with the name 'mbItem201'.

but

_level0.myMenubar.mbItem201.onPress() = function() { ...

produced no error and assigned the click behavior successfully.

Thanks for the nod in the right direction!