Welcome to the WPF feedback portal. We’re happy you’re here! If you have feedback on how to improve the WPF, we’d love to hear it!

Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

Votes

UseNativeFloatWindow causes NullReferenceException when closed in new TabGroup Completed

: Mar 26, 2021 4:08 AM

: May 17, 2021 11:43 PM

: Bug Report

: DockingManager

: 18.4.0.49

: Windows 10

: Vol 1 2021 - SP (May 13, 2021)

: Mar 26, 2021 4:08 AM

: Bug Report

: DockingManager

Requirements:

DockingManager with DocumentContainer enabled.
Creation of horizontal or vertical Tab Groups is allowed. Floating windows is allowed.
IsVS2010DraggingEnabled = true
UseNativeFloatWindow = true
Documents get removed from dockingManager.Children when State = Hidden, as per this guide:
https://www.syncfusion.com/kb/2735/how-to-release-memory-in-dockingmanager-after-closing-the-tab
At least 2 tabs are created.

How to reproduce (on sample project):

Drag a tab to the right side of the window, so that you create a new vertical Tab Group.
Close the tab on the right Tab Group.
_dockingManager.Children.Remove(sender) will raise an NullReferenceException.

Notes:

Bug only occurs when using native float window.
Seems to only occur when using dragging to create the Tab Group. Even if you first create a float window by right-clicking, then the Tab Group by right-clicking, it will not occur.

DockingManagerTest.zip

2 COMMENTS