When you have set the Windows task bar to auto-hide and you maximize an RadRibbonWindow, you are not allowed to visualize the task bar on top of the RadRibbonWindow. Available in LIB version: 2015.1.2303
When the Taskbar is auto-hidden, if the RibbonWindow is maximized, the task bar cannot be displayed.
We have a RadRibbonWindow. When it is run on Windows XP (or on Windows 7, "Windows Classic" theme) and the DPI settings are high (above 170 %), the standard window buttons (Minimize, Restore and Close) are not displayed properly (they are cut). Also there is too much space between them.
Title bar (including the Contextual tab header) goes over the Window (MinMaxClose) Buttons
Output error in VS: System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='Telerik.Windows.Controls.RadRibbonView', AncestorLevel='1''. BindingExpression:Path=IsHostedInRibbonWindow; DataItem=null; target element is 'WindowTitle' (Name='WindowTitle'); target property is 'NoTarget' (type 'Object')
When desktop is shared through Office Communicator 2007 RibbonWindow is not repainting properly. The same issue can be reproduced through a remote desktop connection - when the RibbonWindow is running in a Aero Windows theme, the RibbonWindow chrome is painted in black when accessed through a remote desktop.
When ribbon is placed on two monitors the minimized popup is misplaced.
In WPF the WindowsFormsHost control is displayed on top of the Backstage menu Reason for declining: The WindowsFormsHost element is drawn on top of any Adorner elements. As the RadRibbonBackstage is an Adorner the WindowsFormsHost is drawn on top of it. As a workaround to this framework limitation you could bind Visibility of the WindowsFormsHost to the IsBackstageOpen property of the RadRibbonView and collapse/hide it when the backstage is open. You can find more information about the WindowsFormsHost and its features and limitation in this article ( http://msdn.microsoft.com/en-us/library/ms744952.aspx ).
In a two monitors scenario the ApplicationMenu appears on the left monitor when the RibbonView with negative left margin is hosted in a RibbonWindow which is maximized on the right monitor. EDIT: We are closing this issue as the described behavior as expected. When logged first, the negative left margin of RibbonView was not taken into account. When popup opens and its parent starts on the left monitor, popup calculates that it cannot fit entirely and changes its direction of opening. This expected by the WPF Framework. When you give negative left margin of the RibbonView, its application button might also goes with 1-2 (or more) pixels on the left monitor. Then popup (the application menu opens in a popup) has no space and changes its opening direction to left. This is expected and the only reasonable solution would be changing the negative left margin to positive or 0.
The Title of the RadRibbonWindow is not diplayed unless there is a RadRibbonView in the window.
You can not click the ColorPicker when it is inside a RadRibbonSplitButton.
When maximized (or when dragged from maximized), RadRibbonWindow ,might not render it's chrome. Reproducable on Windows 7, 64bit machine.
Add a possibility to imitate fullscreen mode.
The BackstageItems are not rendered as expected when the RadRibbonView is hosted in apanel with flow direction set to right to left.
Currently, when the users hover around the window's border, the resizing border is 1 pixel wide. Create the border wider (higher at top and bottom borders). Workaround: Apply right margin to the content inside the window.
TreeView or DataGrid, or COmbobox is placed in a dropcontent of a RibbonDropDownButton. Item is selected programmatically before the dropdown is loaded. This leads to null reference exception.
ApplicationName is off center when TabStripAdditionalContent contains an element with long text/content
In XP and Windows10, the window goes behind the windows task bar when it is maximized. The problem manifests itself if we set explicitly the "WindowStyle" property of the RadRibbonWindow. With its "default" value, the problem do not exists. It is also reproduced when AllowTransparency = True (it requires WindowStyle = None), which is needed to set a drop shadow effect.