Hi,
Using v7.3 and got s problem whereby no matter what we do the grid displays the columns as they werewhen the datasource (hierarchical binding list) was first bound on one ofthe bands. It looks ok in design view but as soone as we run it we get ALL columns getting shown again. WE had this problem initially under v7.1 where it was much worse but v7.3 seemed to have fixed it, however it started again on one of the grids after we changed soem of the properties on it (none of which should have made a difference). Is this a known problem? Also, where is the default layout for the grid held how is it possible for it to go back to a previous view even after changing it in design mode.
Regards
Jim
Anyone from Infragistics got any ideas on this as it is causing us big problems?
The UltraWinGrid will lose it's layout if the DataSource sends a Reset notification indicating that bound controls need to reset.
Personally, I prefer to use the InitializeLayout event of my grid to do any formatting. That way, I don't have to worry about it.
Could you clarify under what circumstances the grid will lost it's layout AND does it always go back to the original layout when the datasource was first attached at design time even though you may have subsequently changed it at design time? The underlying structure of the datasource isn't changing altough the data contained in it is, we are attaching a hierarchical binding list. What we are experiencing is that it seem to, on an ad hoc basis reset the layout of the grid to show the datasoruce as it was when the grid was first created in run time. You can run the app one time, everything is fine, run it again it goes back to being all screwed up again. So basically in order to determine what is going wrong we need to know under what circumstances the grid resorts to the layout as when it was first attached months ago desgin time.
Hi Jim,
The grid will throw away the existing layout and revert to the default if it receives a Reset notification from the data source. If the grid is losing it's layout in some other case, then this may be a bug. If you can duplicate this behavior, you should Submit an incident to Infragistics Developer Support and include steps on how to do so.
Do you have anyone else reporting this problem? Trying to duplicate it and send an example (it's part of a very large project) will be a nightmare. is it likely the problem is caused by us using hierarchical datasources as we have had a number of problem in the past using these with the Infragistics grid?
I don't know of any other reports to Infragistics Developer Support. I vaguely recall seeing a couple of other reports of this kind of issue on the forums. But I'm not really sure how that helps. Unless we can duplicate the problem, it's almost impossible to determine the cause and fix it.
I've been having a similar problem latery. I'll be working in the grid layout design and will suddenly be dumped out of it, losing every design change made. Another developer in our shop has had the same experience. Reproducing it is next to impossible, but it keeps happening. I thought it might be something in the machine setup or an update, since this has only been happening recently. We build a lot of grids with fields spread over several rows in the same record, and these seem to be the ones causing us grief. I'd had the layout design bail out when I tried to resize a column when one cell didn't quite line up with the column. If I resized that cell first, I could resize the column. Otherwise, it dumped me back at the design wizard without further ado.