BuyLog In
Bug Report T321533
Visible to All Users

Floating DocumentPanel cannot be shown by setting its Closed property to False if it was closed by setting this property to True and the CloseCommand property is used

created 9 years ago

Hi DevExpress team,

I have a DocumentGroup with a region. There I want to display a view (wrapped by a DocumentPanel)
holding an own ribbon menu with a close button.
At first time, the view will be created and added to the region by the region manager.
The view model of the view holds an own close command. As soon as I press the close ribbon
of the view the close command will be executed -> the DocumentPanel.Closed property will be
set to true and the view will disappear. This is still working.
Because the view is only closed (not removed and disposed) I want to reactivate it.
This is done by setting the DocumentPanel.Closed property to false. This was working
with DevExpress 15.1.6 and I think with 15.1.7 too (not sure) but it is not working with
the version 15.1.8.
I think the problem is that the line "DocumentPanel.Closed = true;" will not move the
panel to DockLayoutManager.ClosedPanels collection.
Remark: If I use the cross button (system menu close) instead, it will work (the view will
be in the DockLayoutManager.ClosedPanels collection and can be opened again).

Kind regards

André

Show previous comments (2)
Alexander Russkov (DevExpress) 9 years ago

    Hi Andre,
    Thank you for your clarification. It would be great if you could provide us with code of the adapter you are using.

    Thanks,
    Alexander

    Andrey Marten (DevExpress Support) 9 years ago

      Hello Andre,

      I've reproduced the problematic behavior on our side and forwarded this ticket to our developers for further research. We will update this thread and will inform you as soon as we have any news.

      Thanks,
      Andrey

      AJ AJ
      André Jauche 9 years ago

        All right, Andrey.
        Thanks for the information.
        André

        Sign in to comment on this post

        Answers approved by DevExpress Support

        created 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.

          Sign in to comment on this post

          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.