ContextMenuStrip property ignored?

Set DefaultContextMenuEnabled to false on the syntax editor control.

Ok thanks - it's a bit weird though - most other .NET controls i've come across don't behave in this way - they would assume that if ContextMenuStrip was set then DefaultContextMenuEnabled would be false? Is there some strange reason for this?

Thanks for the help...

Yeah, personally, I'd consider this a bug. I can't think of a single use-case where someone would want to attach a context menu strip and also have the default one pop up on top of their custom one! Anyway, that's how this control happens to work, and it's the least of my worries that this piece behaves a little wierd. I have much more problems with the way the ContextMenuRequested event works than the fact I have to set DefaultContextMenuEnabled to false!

Ok now i'm worried because I've just used that event to set enabled / disabled, as well as to populate a list of menu sub-members based on a library of snippets... any words of wisdom? :)

Well, just let me know if your code works like you expect it to the first time you right-click on the window....

Mine works now, but when I was trying to set the context menu in that event too, it didn't work right if I didn't have the context menu set already before that event fired. The first time the user right-clicked, it wouldn't pop up the menu. It would only pop it up the second and later times (after the code had set ContextMenuStrip to a value).

You'll probably be fine and will never know the difference unless you try to set ContextMenuStrip to different context menus within that event. In that case, I think it will lag you by a right click!

Ok thanks

I don't think i'll have a problem because i'm not switching context menu strips - simply adding / removing items from the existing context menu

Thank you very much for your help - I can see why you're the guru!!

Hey everyone... good conversation here. Per your discussion, we've made two updates for the next maintenance release that should resolve all this:

1) Updated the default SyntaxEditor context menu display code so that it will not automatically occur if there is a ContextMenuStrip set. This one is because that particular code was written back in .NET 1.x days when there was no ContextMenuStrip yet. We never added a check for it in our .NET 2.0 builds.

2) Changed the ContextMenuRequested event so that it fires before the core Win32 code intercepts the context menu message. This allows for proper dynamic updating of the context menu before Windows displays it.

Hope that helps!

Thanks - good to know the history of it too!