I am using a PopupMenuTool as a context menu which works fine when it does not contain other PopupMenuTools. However, when using child PopupMenuTools, the parent closes whenever one of the child PopupMenuTools closes which is not the behavior it should be doing. Please let me know if there is a solution to this because I think it may be a bug. I am using the latest service release of 2010 Vol 3.
I was not able to reproduce this. Are you handling the UltraToolbarsManager.AfterToolCloseup event? If so, it's possible there is some code in there which is closing the entire context menu when the sub-menu closes. If not, it could be a bug.
I have a simliar problem. We have multiple PopupMenuTools as submenues of a UltraToolbar menu and when changing between them via MouseOver the first one opens correctly, but when changing to the next one the whole toolbar menu closes.
I can provide code and a sample video if it helps.
We use Release 11.1
Again, are you handling the AfterToolCloseup event? Can you provide a small sample which reproduces the issue?
Ok... here is the sample app:
I found out, that the problem seems to be WPF dependent because we use the control "by now" in a "WindowsFormsHost" within a WPF window.
As you can see in "WpfApplication1\bin\Debug\UltraWinToolBarSample.exe"
within a "WindowsFormsApplication"
the behaviour is in fact correct.
Only the WpfApplication1.exe shows the behaviour i descriped.
But if you know any workaround to help us, I really would be deeply grateful :)
Thanks for the offered help so far anyway...
Oh I see. This is because the window in which the UltraToolbarsManager exists is not a .Net Form. This scenario is actually not supported directly by the UltraToolbarsManager and requires a derived UltraToolbarsManager to be created. I provided a sample one to help get people started here. You'll probably also have to call Infragistics.Win.Utilities.ForceNativeMessageFilter() once before your main form is shown so the UltraToolbarsManager can get the proper window messages.
Thank you... This workes perfectly for my problem...!
Now the behaviour is correct even with WPFs WindowsFormsHost