Current filter:
                                You should refresh the page.
                                We apologize for the inconvenience. Our ordering system and the support center may be offline for a few hours on Sunday, May 19 due to maintenance tasks.
                                0
                                  • See the attached sample project, which is a variant of the example used for issue Q316305. Run the app and press Save, which will output a file named layout.xml in the bin\Debug directory. Notice that this file includes grid settings for the first of the two grids, but not the second. This accounts for the problems that are described below.

                                    Restart the application, switch to the second grid (DetailView) and move one of the columns up to the grouping area. Switch back to the first grid, then press Save. Restart the app, and press Restore. You will see that the grouping change has not been restored.

                                    Now perform the same steps in the previous paragraph again, but WITHOUT switching back to MainView before saving. This time the grouping change will be correctly restored.

                                    If you rearrange the two windows so that they appear side by side with a splitter, options for both grids will then be saved correctly. The root cause of the problem is that the DXSerializer is walking the visual tree when it outputs the layout structure. When several panes are docked together as multiple tabs, only the contents of the active tab appear in the visual tree, so that is the only tab that the serializer will save data for.

                                Q305537_MultiDXGridsModified2.zip
                                0

                                Hi Sebastian,

                                Thank you for your report and providing the sample project.

                                The problem is that the serialization engine currently processes only elements placed into the visual tree. Since the content of inactive tabs is not placed into the visual tree, these controls are not serialized.

                                Starting from the next minor update for v10.2 (v10.2.9), you can manually provide a list of objects that should be serialized/deserialized. The code below illustrates this approach:

                                	
                                [C#]
                                DXSerializer.Deserialize(new DependencyObject[] { dockManager, grid1 , grid2}, "layout.xml", "DXWpfApplication", null); DXSerializer.Serialize(new DependencyObject[] { dockManager, grid1 , grid2 }, "layout.xml", "DXWpfApplication", null);

                                We understand that this problem is vital for your development, and we can provide you with an intermediate daily build, containing these changes. Just drop us a line if you need this.

                                We will also continue working on this issue, and will check if there is a way to automatically serialize all objects in this situation. Please give us some time to examine whether or not it is possible.

                                Thanks,
                                Vito

                                0

                                Hi Sebastian,

                                Our developers have found a way to fix this problem. The fix will be included in the next minor updates for both v10.2 (v10.2.9) and v11.1 (v11.1.3). If you wish to try the fix immediately, please click the "Request Fix" button. We will publish a daily build, containing necessary changes.

                                I have also noticed that this report is marked as "Private" and so, it is invisible to others. Can we make it public, so that other customers who experience this problem can view it? If we need to delete any private info from this report (for instance, a project you attached), please let us know.

                                Thanks,
                                Vito

                                0

                                Hi Vito, thanks for the response on our issue. Obviously we would prefer a real fix but I understand this is a significant code change given the way the existing implementation relies upon the visual tree. With the workaround is 10.2.9, will it be harmless to pass through a complete list of grids, regardless of whether they are docked as tabs or split panes? If that's possible, then that would make things simpler for us. Also, will this work with floating panes as well as tabbed/split panes?

                                0

                                Sorry, my last response crossed with yours. I will request the fix and give it a try, that's great news, many thanks. Please go ahead and make the issue public, there is no reason for this to be private actually.

                                0

                                (Sorry, I can't see the Request Fix button, can you point me in the right direction please??)

                                0

                                Hi Sebastian,

                                This button will be available as soon as this issue's status is set to Fixed. I have attached a short screencast demonstrating where you can find this button. Please let me know if you need any additional assistance.

                                Thanks,
                                Stan.

                                0

                                Hi Sebastian,

                                Ok, I have made this report public. Thank you for allowing us to publish it.

                                We already prepared a build, containing the fix. It is accessible here:

                                http://downloads.devexpress.com/Share/DXP/110523/DXperience-10.2.8.11143.exe

                                Please try it at your end, and let us know how it goes.

                                Thanks,
                                Vito

                                0

                                Great, that appears to work very well in the context of the sample app. We will confirm whether this fixes the issue with our production code in the next few days, but it certainly looks like it should do, based upon the behaviour in the sample. Many thanks to you and the dev team for a swift response!

                                You must  log in  or  register  to leave an answer

                                Is your intention to post an answer to your own question?

                                • If so, then proceed.
                                • If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
                                • If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.