Hi there
I have a problem with Ultragrid whereby it's losing the column layouts I set at design-time when the app is run. I'm getting this in several places in my app and it seems to occur at random, the grids are working fine, then they just lose their settings, even when that part of the app hasn't been worked on.
I've had a good read through what's been posted previously on this, and I understand that this is probably due to the runtime datasource not matching what was set at design-time. I can't really understand how this would be the case as the full column list displayed at design-time matches up the columns shown at runtime.
My questions are;
E.g.
Parent object is a CustomerClass, and CustomerClass has a child collection of CustomerClass.OrdersList.
The form is bound to the CustomerBindingSource, which has a datasource of CustomerClass
the grid on the form is bound to a OrdersBindingSource, which has a datasource of CustomerClass and a datamember of "OrdersList".
Any help in getting to the bottom of this would be much appreciated, it is driving me nuts!
Hmmm. Because this wasn't really resolved in the product, I am experiencing the same problem. I can reset the all the settings on a grid, run in debug mode and see the changes were in fact saved and implemented. I can see the grid after running the application and see that the formatting was lost.
I am using version 10.3.20103.1000 of the ultragrid for windows.
Setting all these settings at runtime might be a work around but it is not a fix.
Hi Tom,
I do remember. And I'm glad it's all working now. :)
Hi Mike
Thanks for all your help and patience on this one. We just installed 9.2 and suddenly all our issues seem to have (fingers crossed) sorted themselves out. Grids that weren't working are now displaying correctly.
I'm sure you won't remember, but we had issues with ICancelAddNew and IEditableObject previously which have been fixed in this version, I'm wondering if somehow these changes have something to do with it.
Anyway, for the time being the issue seems sorted [:)]
I'm afraid you lost me with that last post. You are starting VS and then getting an error at run-time? And you weren't getting this error before?
If a breakpoint is fixing it, somehow, then I would agree it sounds like a timing issue, but I can't even begin to guess what the issue might be without seeing a sample in action so I could debug it.
Also, I'm not sure that just because the memory usage is going up that there's a leak. There's only a leak if it doesn't go back down again when you close VS. Or if it continues to go up when you repeat the same actions.
Sorry, should have said that the memory leak is occurring at design-time not runtime.