Does anyone know what changed in 15.1 that would cause my tried and true saved grid layouts to not work anymore?
I have ben letting my customers save grid layouts sine I started using Infragistics about 6 years ago.
With the update to 15.1, many of my customers have been getting errors when trying to load their grid layouts. I even had to write code to just delete the layout if it couldn't be loaded.
Could it be that there are some features that have changed enough to invalidate layouts saved from years ago?
We have always used the binary file for the layout, but I am now switching to XML because there no way for me to fix problems in the binary files. Seems like around the same time, a good number of customers have been reporting an increase in the Red "X" on the UltraToolbarsManager, which in my gut, I feelw has something to do with the saved layouts and the grid
Thank you for posting in our forums.
I don’t think anything has changed specifically with the Save and Load methods of the UltraGrid. However it is still possible that some of the features affect them in some way. What errors do your customers get? Can you provide us with a small sample along with one of the problematic binary files, with which I can reproduce the issue on my machine? This will enable me to research this issue and find what is causing it.
Thank you for your collaboration.
I am looking forward to hearing from you.
Since I am deleting the layout if it doesn't load right, I'm not sure what the error was anymore... however, what I'm really getting at is that my customers are getting is the Red "X" in the toolbars. The only thing I can think of is that the grids are everywhere for us and they most of the time have saved layouts, some from many years ago. Or do you think it maybe the Window List in the main menu toolbar (I'm using the TabbedMDI control too). The red x only happens in toolbars, but there must be a root cause for it.
I can't imagine any connection between the loading of a layout in the grid and and toolbar showing a red X. These are two separate controls which have no connection to each other.
The red X indicates that an exception occurred while painting a control. There are two main causes of a red X. The most common cause is the improper use of threading in an application. If you application uses threads and doesn't properly marshal the data across those threads, then you can run into exceptions because the control encountered invalid or unexpected data when painting.
The second potential cause is a bug in the control. We recently did fix an issue that was causing a red X, so it's a good idea to make sure you are using the latest service release.
If that doesn't help, then we would need to be able to reproduce the problem, or at least see a call stack, in order to be able to offer any useful advice.
Regarding the grid layouts not loading properly, a newer version of the grid should be able to load a layout saved with an older version. If that's not working, it's a bug and we can look into it, but we would need to know the exception and have some way to reproduce it. If you have the old layout files, that might help, also.