"Can't change the visibility of the main menu bar"


(Kevin Krumwiede) #1

I created an Advanced Search BAQ. When used, it prompts for its parameter and returns results correctly. But at the moment the parameters are submitted, an error pops up that says, “Can’t change the visibility of the main menu bar.” The full error message is:

Application Error

Exception caught in: Infragistics4.Win.UltraWinToolbars.v12.2

Error Detail

Message: Can’t change the visibility of the main menu bar
Program: Infragistics4.Win.UltraWinToolbars.v12.2.dll
Method: InternalSetVisible

Client Stack Trace

at Infragistics.Win.UltraWinToolbars.UltraToolbar.InternalSetVisible(Boolean newVisibleValue, Boolean bypassDockUpdateForMergedToolbars)
at Infragistics.Win.UltraWinToolbars.UltraToolbar.set_Visible(Boolean value)
at Ice.UI.Dashboard.DashboardPanel.InitializeLaunch()
at Ice.UI.Dashboard.DashboardPanel.firstPanel_Paint(Object sender, PaintEventArgs e)
at System.Windows.Forms.Control.OnPaint(PaintEventArgs e)
at Ice.Lib.Framework.EpiUserControl.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Google has exactly one result for this error message. It’s a Q&A on the Infragistics site.

I don’t think there’s any way my BAQ could cause this. Could this be an E10 bug? I’m on 10.2.100.8.


(Phil Leaman) #2

Kevin -

Were you able to resolve or workaround this error? I am having same problem and would be curious your outcome.

Thanks
Phil


(Kevin Krumwiede) #3

I never found a solution. As with so many other E10 quirks, users just incorporated ignoring it into their workflow.