We have an ultrawingrid that is on an ultratab. The UWG is located on the second tab. The grid is loaded in the from load event.
The UWG's first column has a checkbox header. We have a call which enables a save button in the AfterHeaderCheckStateChanged event.
When we change the tab to the second tab the AfterHeaderCheckStateChanged event is being fired.
1. Is there a better place to locate our save button call then in the AfterHeaderCheckStateChanged function?
2. What event on the grid fires the AfterHeaderCheckStateChanged event after changing tabs?
Thanks!
Justin
Mark,
Selecting a different tab shouldn't cause the AfterHeaderCheckStateChanged event to fire. That event will fire when the user clicks on the check box in the header and changes its state. I am sending you a simple application which attempts to reproduce what you have described. Check it out and let me know if I am doing something drastically different from what you are doing. Maybe you could modify it to cause it to reproduce the behavior you are seeing in your own application and then send it back to me.
Let me know if I can be of further assistance.
Michael S.
We've tried that.
This grid is loaded on the form load and at the point when we switch tabs we have no logic affecting the grid. When we added the breakpoint it does not appear that anything is triggering that event.
We are new to Infragistics controls, so sorry if we are missing something but we are stumped here.
You might want to put a breakpoint in the AfterHeaderCheckStateChanged handler to see what is triggering the firing. From what I remember, a change in value of any of the cells in that column could cause the header check state to change, and if that is what is happening, it is functioning correctly.
If you are triggering the event, you could place the code that is causing that in a try/finally block, and set/clear a flag that signifies not to process anything in the AfterHeaderCheckStateChanged handler.