We have identified a bug with the RadPane/RadDocking control's maximize functionality, which we would appreciate your feedback on as soon as possible.
When maximizing a floating RadPane on a secondary display that has a resolution greater (1920*1200) than that of the primary display (1600*1200) the RadPane is not sized to the extent of the display, but extends beyond it. This is only the case when the resolutions of the displays are setup in this way; if the primary screen has the greater resolution it does not occur. Unfortunately this is a usual setup for laptop users who have a large display available when they are working in the office.
However, we have resolved this issue (or very similar) in the past in some of our own window management code, so may be able to offer a potential resolution. We experienced the same symptoms in our custom windows as a result of using a WindowStyle of None and then using Win32 interop to set the minmaxinfo appropriately to avoid overlapping the Windows TaskBar. The calculations for some reason became invalid in the scenario described above. The solution implemented was simply not to adjust the minmaxinfo when the window was found to be not on the primary screen.
Looking forward to your feedback,