That did the trick. Thanks for your help!

I see why my logic is faulty - you can hover twice or more to expand the child menu items. I do understand your suggestion to push the node down to the next level and set it up as a node with no children.

I did notice the "Add to" on your script but didn't quite understand how that helped - I'll look at it again more closely.
I was also thinking you could check for three situations/conditions where you could consider the OnClick valid:
1. Event triggered on a Node with no children - obvious
2. The same node (with children) was triggered twice in a row (once to expand and the second a mouse click)
3. The node was already expanded

Your "ideal world" is not ideal for all of us. Anyway, you should send your complains to William Henry Gates III, because he is responsible for such behavior, not MM developers. ;)

A solution is really simple, as onenonymous already explained, you should not assign OnClick event handlers to menu items which have sub-menus. Because you need to have a possibility to select such items as well, you should add one new item on the top of their sub-menus on which you could click instead. If you don't know what I am talking about, just take a look at the Send To / Playlist menu which has[b] Add to ...[/b] item on the top of every sub-menu. I am using similar approach in my script and this works just fine.

Well I disagree. The event is called OnClick and should therefore be triggered once on a mouse click. But apparently that's not the case. Ok, so it's not an ideal world. But since that's the way it is, fine. What I did to try to work around that is still use the onclick event and whenever it got triggered I saved the playlist title to a variable. The problem I'm having is distinguishing a real mouse click from an event triggered from 'hovering'.

[quote="raybeau528"]Bad implementation or working as designed?[/quote]
Which bad implementation? I think you didn't understand, I said this behavior is not exclusive to MM. I just tried Visual Basic and as I supposed it generates OnClick event when you just hover with a mouse above the menu item which has sub-items. And as I explained with the keybard events, OnClick event is obviously generated on many other occasions when you even don't use a mouse.

I don't understand what you want to say with your explanation about the Send To menu. You don't know what is happening internally to MM when a user hover with a mouse above the Send To item. Because nothing is happening, it doesn't mean that OnClick event was not generated in that case. Most probably, MM generates OnClick event in that case, but MM simply ignore it. I am doing the same thing with my playlist menu in the Export M3Us/Create Playlists for Child Nodes and you should do the same thing. I don't know why this is so big deal for you.

Bad implementation or working as designed?

But if you right click on a playlist or selection or whatever and you select Send To you get multi-level menu items of which you can follow the tree up and down and in and out without anything happening until you actually click on an item. I guess that's what's meant by "OnClick" ! :) If only the API was implemented the same way.

[quote="raybeau528"]Isn't that what "OnClick" means?[/quote]
I don't remember how menu item with sub-menus works within Visual Basic and other programming languages, but I suppose that they have same behavior as MM menu. Similar thing happens with the [url=http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=36597&start=0&st=0&sk=t&sd=a&hilit=onkeypress]keyboard events[/url]:
when we press a key on some button in Visual Basic (and hold it some time), we have the next order of events:
- OnKeyDown
- OnKeyDown
...
- OnKeyDown
- OnKeyUp
- OnClick

You see? There is an OnClick event, even if you don't touch a mouse, just keyboard!

[quote]couldn't you test for whether item 2 would have sub-items, and if so, not assign the OnClick event?[/quote]
I certainly could, though it would be very difficult to 'look ahead' down the tree but that won't help because I need to click on every item whether it has child playlists or not. Consider the "Send To" option - you can click on the parent playlist or a child playlist. That's the behavior I need as well.

[quote]better way how to detect when some playlist is added/removed, since there not exist OnPlaylistAdded and OnPlaylistRemoved events[/quote]
Exactly. I have to rebuild the all the menu items every time. What's really needed is an "onfocus" event to execute for those times when you do want the event automatically triggered but the onclick event should only be triggered when you actually click it. Isn't that what "OnClick" means? I also tried the "OnMouseUP" or "OnMouseDown" events available under SDBUICommon but apparently that doesn't apply to the menu items because they just do the old NOP routine - it doesn't error, it just doesn't do anything.

[quote="raybeau528"]Is this a bug? ... This is not desired behavior.[/quote]
Well, I don't think it is a bug and it is desired for me, at least on the first level. I have created same menu with playlists like you and it is constructed dynamically, so I need to be able to recreate it using exactly that event. I am using it like that because I don't know for better way how to detect when some playlist is added/removed, since there not exist OnPlaylistAdded and OnPlaylistRemoved events.

If you have used Windows 3.x or earlier, you know that it was required to click on the main menu to get its sub-menu - with Win95 it was introduced that its is enough just to hover mouse above main menu to get its sub-menu. Obviously, MM follows Win3.x logic ;)

couldn't you test for whether item 2 would have sub-items, and if so, not assign the OnClick event?

I'm creating menu items to emulate the playlist tree and assigning an "OnClick" event to each menu item. When I right click on the main menu item in the playlist tree and move the cursor to items that don't have sub-items and click that menu item it invokes the event just fine. When I move the cursor to an item that does have sub-items the event is triggered automatically without actually clicking. How can I avoid the event being triggered automatically? Is this a bug?

For example:

item1
item2
item2a
item2b
item3

If I click on item1 or item3 it works fine. But as soon as I land on item2 it triggers the event immediately. This is not desired behavior. I want to be able to click on item1 or item2a etc without automatically triggering the event.

Any ideas?

Thanks!