Having Problems with unreadable Tabs in RadPaneGroup: TabsSqueeze.png
I think I found a Solution with OverflowMode and ScrollViewer:
<telerik:RadPaneGroup x:Name="DocumentGroup" ScrollViewer.HorizontalScrollBarVisibility="Auto" OverflowMode="Scroll">
Problem:
After Loading Layout the OverflowMode is not respected anymore.
I found this ticket in Silverlight, what discribes the Problem and is approved: Docking: I would like OverflowMode to work for all RadPaneGroup in xaml/codebehind and this be persisted through SaveLayout/LoadLayout
And i found this documentation, which say, using OverflowMode can lead to unexpected behaviors:
https://docs.telerik.com/devtools/wpf/controls/raddocking/general-information/not-supported-properties
so i report this as a feature instead of a bug.
Please sea atteched an example project: TabWrapProblem.zip
Usage: Save and than Load the Layout -> Scrolling of tabs break
After upgrading to Telerik WPF 2019.1.116 from 2018.3.1010 we receive a lot of:
System.ComponentModel.Win32Exception (0x80004005): Invalid window handle
MS.Win32.UnsafeNativeMethods.GetWindowText(HandleRef hWnd, StringBuilder lpString, Int32 nMaxCount)
Exceptions. It makes out application very slow.
In version 2018 everyting was OK. See attached scerenshots.
Got this weird behavior with RadDocking with multiple monitors. http://www.youtube.com/watch?v=8DDX5OiYRyM As you could see the pane is being opened on the wrong side. This happens only when the application is fully maximized, if its resized then this problem does not occur. I am not able to reproduce this with a simple example. But you could contact me I can help in investigation.
Is there any option to create a connection line as a blank rectangle. At present I can see only solid lines only. Please see the attached image, and suggest how to get top two connection types. Decline reason: The diagram exposes an API that allows you to create custom geometry for the connection. You can override the CreateGeometry(), CreateSourceCapGeometry() and CreateTargetCapGeometry() methods of RadDiagramConnection and create custom geometries. See the CustomConnectionCap SDK example: https://github.com/telerik/xaml-sdk/tree/master/Diagram/CustomConnectionCaps
RadPane setting CanFloat, CanUserPin & CanUserClose to false, ContextMenuTemplate="{x:Null}" and PaneHeaderVisibility="Collapsed" still leaves a small part of the header visible and clickable. If there is any work-around can you please let me know. Version 2014.3.1202.45, using Framework 4.5 with VS2013.
I have a scenario where I only want to unhide the pane when certain property of the document is true. For example: I have 3 panes A,B and C Panes A and C are visible. Active Pane should always be Pane A. By default pane (B) is hidden. Now when I set the IsHidden Property of the pane B to FALSE. Pane B now becomes the active pane. I still want Pane A to be the Active Pane, but show the Pane B in background. If I try setting the Pane A to be the active pane after Pane B is shown. It flickers which you can see here http://screencast.com/t/dGvU7UwUyYp Is there any way i can unhide the pane in background while the active pane remains the same without having this flickering scenario.
Exception is thrown when running RadDocking in separate thread.
An access key can be added to ContentPresenter in WPF if you add underscore in the content and set RecognizeAccessKey to true.If the ContentPresenter is inside DocumentHost, the access key is working, but the underscore in the UI is not visible. If you remove the DocumentHost everything works as expected.
If a SplitContainer's InitialPosition is set to FloatingDockable and the the layout is saved in the Unloaded event of the control, that SplitContainer is not shown after layout load. The same could be observed if you float a Pane by dragging it out of its docked state.
When all of the RadDocument panes in the DocumentHost are closed the last one stays alive in .Net Framework 4.0. The issues can't be reproduced on machines with .Net Framework 4.5 installed
The text in the Alt+Tab Manager is empty when there is a floating Pane in Windows XP
Panes that are autohidden are cut if resized too much - this is due to limitation in WPF that popups should not cover more than 75% of the screen.