On some computers we see some strange effects when our WPF-Application is maximized.
(System.Windows.Window.WindowState==WindowState.Maximized).
These effects include:
- Misplaced Popup-Windows like menus (main and context menus), tooltips ect.
- Rendering errors
- No reaction on mouse-hover (e.g. over buttens or other controls)
- 100% CPU usage (of one CPU-core). Remote debugging showed an endless Measure/Arrange of an embedded ScrollViewer Control.
- slow reaction of the application (propably caused by the 100% CPU usage)
Scaling the application in normal mode to use (nearly) the same space as miximied does not show these effects.
There are some disucssions (with example code) but no usefull solution:
http://social.msdn.microsoft.com/Forums/en/wpf/thread/68df2ad0-d6b5-44d4-9ea8-e10cfa6bad47
http://social.msdn.microsoft.com/Forums/pl-PL/windowsuidevelopment/thread/545461b5-cf62-48e2-bcfb-2e872ecea639
http://social.msdn.microsoft.com/Forums/en/wpf/thread/fc1d99aa-e331-4d15-81b5-0a091bfa2efb
(maybe the same problem, I'm not sure)
http://social.msdn.microsoft.com/Forums/en/wpf/thread/ab6985cb-fb49-414f-85f3-14d702fe69ca
(including an example and screenshots of the effect)
I made a Microsoft-Connect Entry nearly two month ago, but no reaction from Microsoft so far.
We would like to know:
- What is the root cause for this problem (has this something to do with the VisualScrollableAreaClip-Property) ?
- What can well tell our customers how to avaid this problem (except of not using Maximize, which is the default for our application) ?
Thank you for helping...
(System.Windows.Window.WindowState==WindowState.Maximized).
These effects include:
- Misplaced Popup-Windows like menus (main and context menus), tooltips ect.
- Rendering errors
- No reaction on mouse-hover (e.g. over buttens or other controls)
- 100% CPU usage (of one CPU-core). Remote debugging showed an endless Measure/Arrange of an embedded ScrollViewer Control.
- slow reaction of the application (propably caused by the 100% CPU usage)
Scaling the application in normal mode to use (nearly) the same space as miximied does not show these effects.
There are some disucssions (with example code) but no usefull solution:
http://social.msdn.microsoft.com/Forums/en/wpf/thread/68df2ad0-d6b5-44d4-9ea8-e10cfa6bad47
http://social.msdn.microsoft.com/Forums/pl-PL/windowsuidevelopment/thread/545461b5-cf62-48e2-bcfb-2e872ecea639
http://social.msdn.microsoft.com/Forums/en/wpf/thread/fc1d99aa-e331-4d15-81b5-0a091bfa2efb
(maybe the same problem, I'm not sure)
http://social.msdn.microsoft.com/Forums/en/wpf/thread/ab6985cb-fb49-414f-85f3-14d702fe69ca
(including an example and screenshots of the effect)
I made a Microsoft-Connect Entry nearly two month ago, but no reaction from Microsoft so far.
We would like to know:
- What is the root cause for this problem (has this something to do with the VisualScrollableAreaClip-Property) ?
- What can well tell our customers how to avaid this problem (except of not using Maximize, which is the default for our application) ?
Thank you for helping...