Bug Report T323533
Visible to All Users

DocumentRemoved and DocumentClosed events are raised in incorrect order

created 9 years ago (modified 9 years ago)

[DevExpress Support Team: CLONED FROM T321093: How to share one RichEditControl toolbar between several RichEditControls]
Please see video. This is the same project. But after updating from 14.1.8 to 15.2.4 it does not work properly.
When I open one document and close it then the first raised event is DocumentRemoved (DocumentClosed expected).
When I open two or more documents and close them one by one then then the first raised event is DocumentClosed (as expected), but Documents.Count contains wrong value.
As a result, the main window does not close after the last document has been closed.

Answers approved by DevExpress Support

created 9 years ago (modified 9 years ago)

We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

    Comments (2)
    DevExpress Support Team 9 years ago

      Hello Andrey,
      Would you please uncheck the Private flag so we can include this fix in our What's New ?

      DevExpress Support Team 9 years ago

        Thank you for your cooperation.

        created 9 years ago

        I have created a sample project and tested it in all versions starting with 14.1.8. The order of the events in all versions is the following:

        1. DocumentClosing
        2. DocumentRemoved
        3. DocumentClosed
          I've also created a sample video to demonstrate that.
          It seems the cause of the issue is the code in the project. Please check it and let me know your results.
          Comments (2)
          AK AK
          Andrey Kushnarev 9 years ago

            Unfortunately I already removed 14.1.8 version, but I still use sometimes 13.2.8 version and with small modifications in your project I reproduce my issue in my side

            DevExpress Support Team 9 years ago

              Thank you for the clarification. I've successfully reproduced the behavior you described and passed the ticket to our developers for further research. We will inform you as soon as we have any results.

              Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

              Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.