We noticed that floating documents never use the corresponding highlight state.
There seems to be a initilization problem with floating windows, especially documents for that matter.
I looked into the source and was able to hotfix the problem.
FloatingDocumentWindowControls apply the themes in the constructor but the datatrigger that updates the highlight-state of floating-documents depends on the implemented abstract property 'LayoutDocumentFloatingWindowControl.Model'. If you move the application of the theme to the inheritors constructor the databinding is working again.
It would be great if this gets fixed fast so we don't have to use a hotfixed version for to long. Additionally we can't really confirm that this fix is not causing other problems.
Corresponding DataTrigger can e.g. be found in:
-> ExtendedWpfToolkit SourceCode at Rev. 117060
-> Xceed.Wpf.AvalonDock.Themes.Aero
-> Theme.xaml Line 1063
Comments: ** Comment from web user: aherzog **
There seems to be a initilization problem with floating windows, especially documents for that matter.
I looked into the source and was able to hotfix the problem.
FloatingDocumentWindowControls apply the themes in the constructor but the datatrigger that updates the highlight-state of floating-documents depends on the implemented abstract property 'LayoutDocumentFloatingWindowControl.Model'. If you move the application of the theme to the inheritors constructor the databinding is working again.
It would be great if this gets fixed fast so we don't have to use a hotfixed version for to long. Additionally we can't really confirm that this fix is not causing other problems.
Corresponding DataTrigger can e.g. be found in:
-> ExtendedWpfToolkit SourceCode at Rev. 117060
-> Xceed.Wpf.AvalonDock.Themes.Aero
-> Theme.xaml Line 1063
Comments: ** Comment from web user: aherzog **
After reviewing the issue again and testing it witch the LiveExplorer test app, i noticed that there is no highlighting of docked out documents at all when it does not contain any child that can get keyboard focus. This is a problem when the content is some kind of custom rendered view. In the case of anchorables this problem is not present because the surrounding pane evaluates the mouse clicks and causes highlighting of the window.
Floating Documents on the other hand don't have the ability to be grouped and so they have no pane and only the keyboard focus gets evaluated.