By advance, excuse-me because I'm a new user of CodePlex (so I don't know how to report an issue), and because I'm... French, so my english can be bad very often !! YeWell, here's the issue:
When a DockingManager is created but is never visible (for example in a TabItem of a TabControl), _autoHideWindowManager member stays null. But when this DockingManager is unloader, the event handler DockingManager_Unloaded is called and there is an exception on "_autoHideWindowManager.HideAutoWindow();" line since _autoHideWindowManager is null.
I think that this code :
if (_autoHideWindowManager != null)
{
_autoHideWindowManager.HideAutoWindow();
}
should be better to manage this case (DockingManager never visible before to be unloaded)
Comments: ** Comment from web user: oponsinet **
When a DockingManager is created but is never visible (for example in a TabItem of a TabControl), _autoHideWindowManager member stays null. But when this DockingManager is unloader, the event handler DockingManager_Unloaded is called and there is an exception on "_autoHideWindowManager.HideAutoWindow();" line since _autoHideWindowManager is null.
I think that this code :
if (_autoHideWindowManager != null)
{
_autoHideWindowManager.HideAutoWindow();
}
should be better to manage this case (DockingManager never visible before to be unloaded)
Comments: ** Comment from web user: oponsinet **
Dear all,
I'm now using the last AvalonDock version (2.0.2000) and this issue is still present :-( ! __I thought it should be fixed since it's so simple and safe to correct__... __I don't know how to get it fixed ! I should have set this issue impact to high since it is the case for me : I'm using some DockingManagers in different TabItems and I have a crash each time the user don't select at least one time each TabItem !__
So I'm one more time oblized to download the source code, to add this correction, and to use my modified version of AvalonDock... It's not a clean solution... But it's the only one which works !
BR
Olivier.