Hello,
We are using UltraWinExplorerBar.UltraExplorerBar. And we have to hide the customize button at the bottom of explorer. We have used the below code to hide the customize button.
UltraExplorerBar1.NavigationOverflowButtonAreaVisible = False
Now when we click on the some areas at the bottom of explorer its giving the following exception.
ActiveGroup cannot be set - specified Group cannot be activated! (Group may be disabled or its header may not be visible)
System.ArgumentException was unhandled Message="ActiveGroup cannot be set - specified Group cannot be activated! (Group may be disabled or its header may not be visible)" Source="Infragistics2.Win.UltraWinExplorerBar.v10.3" StackTrace: at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.set_ActiveGroup(UltraExplorerBarGroup value) at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBarGroupHeaderUIElement.OnMouseDown(MouseEventArgs e, Boolean adjustableArea, UIElement& captureMouseForElement) at Infragistics.Win.ControlUIElementBase.ProcessMouseDownHelper(Object sender, MouseEventArgs e) at Infragistics.Win.ControlUIElementBase.ProcessMouseDown(Object sender, MouseEventArgs e) at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e) at Infragistics.Win.UltraControlBase.OnMouseDown(MouseEventArgs e) at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.OnMouseDown(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun() at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel() at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine) at UltraExplorerBarError.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81 at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args) at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
We tried various events to handle the exception, but could not trace any event to handle the exception.
Please suggest a solution to handle this exception.
I just re-read the thread and noticed the trace was there and it looks like this is the issue that was fixed in build 2112. Double check your build of the 10.3 assembly you are using and if it is less than 2112 you need the latest hotfix and it should be resolved. I'm still not sure why I wasn't able to reproduce it in my testing with this fix undone. If you can attach a sample that reproduces the exception I can verify against the builds.
I haven't been able to reproduce this myself yet but I did notice that we made a change in 10.3 build 2112 that handled an exception of this kind in the OnMouseDown handler of the GroupHeaderUIElement. I undid the change and tried to reproduce what you are seeing and it still wasn't reproducing the exception.
What does the stack trace look like for the exception there? What build of 10.3 are you using?
I'm unable to insert the screen shot here. Below is the link of the file showing the area where i'm clicking and the error.
https://www.box.com/s/8zhw502nojr1288me8bm
With that property set doesn't the whole bottom area go away and there is no way for the user to activate that group now? Where are you clicking? Are you activating the group through code? Can you post a screenshot that accompanies this exception and show where you clicked?