Current filter:
                                You should refresh the page.
                                Support Center
                                Show all comments
                                • Andreas Mummenhoff 02.24.2017
                                  If you invoke the SwitchMasterDetailMode action from the context menu (WinForms), the context menu stays open
                                • @Andreas: I've created a separate ticket on your behalf (T486898: Context menu stays visible after using a solution from S173664) and just answered it. Thanks.

                                • Kim_Schmidt 05.03.2017
                                  Hello DevExpress team,

                                  this API extension is very useful, thank you. But there is one problem - It works fine until i have a ListView in Server-Mode (Model -> DataAccessMode = Server). In this case i get InvalidOperationException "Cannot change DefaultSorting property...". This problem is already known ( Do you plan any further APi improvement because of this exception, or what could you suggest us in this situation?

                                  Thank you and best regards.

                                • @Kim_Schmidt: Thanks for your feedback on this new solution - our Core team and I are happy to hear that this is useful for your business.
                                  As for the behavior you experienced, we already made additional checks in our code to avoid it in the most popular cases: The "Cannot change property 'DefaultSorting' when the XPCollection is not in design or initialization mode." error occurs in MainDemo. I have just made sure it was corrected for this particular code after testing the latest v16.2 bits.

                                  Take special note that if you explicitly modify the IModelListView.Sorting node or apply sorting to the CollectionSource directly (we think it falls to rare and advanced scenarios), you will not avoid this exception as expected. Let me know if you think this behavior can be improved further.

                                • Kim_Schmidt 05.05.2017

                                  Hello Dennis,

                                  Yes, this feature is quite important for our application, so thank you again for working in it.

                                  Unfortunately, after careful testing, I noticed that we can’t use this improvement in our application yet. I found some problems and gathered them in attached solution. For now we stay with “old” approach – recreate view.

                                  1. Problem – start ListView “Test Bo 1” and execute 2 times action “SwitchMasterDetailMode” -> NRE should be thrown. This is a small bug, I guess.

                                  2. Problem – start ListView “Test Bo 2” and execute action “SwitchEditor”… OK, the problem is understandable, but what to do with it? Now we avoid this problem, because we set DataAccessMode = Client to the View.Model during View recreating if the editor does not support server mode. In case with Frame.SetView(...) without View recreating it does not work, because the collection source of the View is already created. I didn’t find any solution for this scenario, but just forbid the action if desired editor can’t work in server mode is not the appropriate solution for us.

                                  3. Problem – start ListView “Test Bo 3”. The view stated already in master-detail mode and if you click on the “Prop Bool” check box, you will be notified about very important code execution. Now execute “SwitchMasterDetailMode” action twice, click “Prop Bool” again – nothing happens. To understand this please take a look to the MyVeryImportantController in the attached solution, I wrote some comments there in source code.
                                  I can understand this problem as well, and I can even avoid it with extending of MyVeryImportantController with Frame.ViewChanged event handler, for example, but the problem is – we have a lot of controllers, which track the current object changes... I wish to have some option to notify all such controllers, and in my opinion it could be View.CurrentObjectChanged event, but I couldn’t find any chance to force it – any manipulation with GridView.FocusedRowHandle were unsuccessful.

                                  Let me know if description of my problems was insufficient, I’ll give you more details.

                                  Thank you for your assistance and best regards.

                                • Thanks for your update. I need some additional time to research your code and issues with it. Please bear with me.
                                • Hello,

                                  1. I've created a separate ticket on your behalf (T512772: TreeListEditor - NullReferenceException occurs on the second ListView recreation after changing the corresponding Application Model node) and responsible developers from our Core squad will work on a fix.
                                  2. I've just described an alternative solution in the T512781: How to switch between TreeListEditor and GridListEditor in a ListView with DataAccessMode = Server and avoid InvalidOperationException (X does not support Server Mode) ticket.
                                  3. I've created a separate ticket on your behalf (The View.CurrentObjectChanged event is not raised on the second ListView recreation after changing the corresponding Application Model node) and you will be automatically notified once we finish our research.

                                0 Solutions

                                Creation Date Rating Importance Sort by

                                If you need additional product information, write to us at or call us at +1 (818) 844-3383

                                FOLLOW US

                                DevExpress engineers feature-complete Presentation Controls, IDE Productivity Tools, Business Application Frameworks, and Reporting Systems for Visual Studio, along with high-performance HTML JS Mobile Frameworks for developers targeting iOS, Android and Windows Phone. Whether using WPF, ASP.NET, WinForms, HTML5 or Windows 10, DevExpress tools help you build and deliver your best in the shortest time possible.

                                Copyright © 1998-2017 Developer Express Inc.
                                All trademarks or registered trademarks are property of their respective owners