Recently Updated
Unplanned
Last Updated:
30 Sep 2024 11:28
by ADMIN
Created by:
Eddie
Comments:
1
Category:
Dock
Type:
Bug Report
In this case, we add a ToolWindow directly to the control in a floating state using FloatingWindow. Each add ToolWindow will have a different BackColor property value. Now we save the layout of the control into an XML file. The next step is to close the application and load the layout from the XML. The ToolWindows are loaded, however, their BackColor property is not restored.
Unplanned
Last Updated:
01 May 2024 09:57
by ADMIN
Created by:
Bert
Comments:
1
Category:
Dock
Type:
Bug Report
In this case, we have 5 MDI children and the last one is active. Closing the first one from the tab close button will activate the second child. Closing a non-active child should not change the active window in MDI scenario.
Unplanned
Last Updated:
22 Apr 2024 10:05
by ADMIN
Created by:
Michael
Comments:
1
Category:
Dock
Type:
Bug Report
this.toolWindow1.TabStrip.MinimumSize = new Size(200,200)
Unplanned
Last Updated:
09 Jan 2023 13:37
by ADMIN
Created by:
Kris
Comments:
1
Category:
Dock
Type:
Bug Report
All you need to do to reproduce the issue is to run, close, run, close several times - maybe 5 or more times, and observe the floating windows increasing in size.
Unplanned
Last Updated:
26 Dec 2022 11:08
by ADMIN
Created by:
Kris
Comments:
1
Category:
Dock
Type:
Feature Request
Currently, when you load a layout and the XML contains a lot of windows, even though they may not all be visible, I have to set the Visible property to false on the RadDock control to eliminate some funky refreshes are visible to the user (something we want to avoid). I also wanted to mention that using SuspendLayout/ResumeLayout instead of using Visible=false/true does not work. Maybe this is something the development team can investigate at some point as well.
Unplanned
Last Updated:
16 Sep 2022 07:07
by Ark Technologies
Created by:
Ark Technologies
Comments:
0
Category:
Dock
Type:
Bug Report
In this particular case, a HostWindow is hidden in the Loaded event of the Form. When we save the layout and load it again, the wrong autohide window is shown. The HostWindow.Hide() method in the loading scenario is forcing the wrong AutoHide HostWindow to be shown.
Unplanned
Last Updated:
08 Aug 2022 11:12
by Mark
Created by:
Mark
Comments:
0
Category:
Dock
Type:
Bug Report
The problematic tool window has a user control that is docked to fill and it is built entirely with Telerik controls. The dock control, tab strips, windows and even the controls inside the user control are correctly scaled. The issue comes when you start undocking and then docking the tool window. The size of the user control increases with each operation. The controls have anchors and although they have correct scaling they get stretched. This results in messed layout.
The DocumentTabStrip and ToolTabStrip are created dynamically and when they initialize they call their Scale method. The tool window, the user control, and also all other controls added to it are created only once. When you undock the window a new tab strip is created and the existing controls are added to it. When we load the tab strip we call PerformRadAutoScale which calls the stip's Scale method. Calling Scale propagates to the child controls causing additional scaling to the Microsoft controls. RadControls don't have issues because we have logic to check the scaling of the window and we don't allow double scaling.
As a workaround, we can create custom tab strips and override the ScaleChildren property to return false.
The DocumentTabStrip and ToolTabStrip are created dynamically and when they initialize they call their Scale method. The tool window, the user control, and also all other controls added to it are created only once. When you undock the window a new tab strip is created and the existing controls are added to it. When we load the tab strip we call PerformRadAutoScale which calls the stip's Scale method. Calling Scale propagates to the child controls causing additional scaling to the Microsoft controls. RadControls don't have issues because we have logic to check the scaling of the window and we don't allow double scaling.
As a workaround, we can create custom tab strips and override the ScaleChildren property to return false.
this.radDock1.DockTabStripNeeded += this.RadDock1_DockTabStripNeeded;
private void RadDock1_DockTabStripNeeded(object sender, DockTabStripNeededEventArgs e)
{
if (e.DockType == DockType.ToolWindow)
{
e.Strip = new MyToolTabStrip();
}
else
{
e.Strip = new MyDocumentTabStrip();
}
}
public class MyToolTabStrip : ToolTabStrip
{
protected override bool ScaleChildren => false;
}
public class MyDocumentTabStrip : DocumentTabStrip
{
protected override bool ScaleChildren => false;
}
Unplanned
Last Updated:
21 Apr 2022 05:32
by ADMIN
ADMIN
Created by:
Stefan
Comments:
1
Category:
Dock
Type:
Feature Request
Use cases: 1. You have a MainDocumentContainer with Document windows in it, placed in one under the other. Setting the DockState of the bottom DocumentWindow to Hidden, and restoring it afterwards, should place the DocumentWindow at the same place, instead of merging it with the above one 2. Same layout as above, when the layout is saved and then restored, the DocumentWindow positions should be exactly as they were
Unplanned
Last Updated:
02 Feb 2022 12:27
by ADMIN
Created by:
Kumaran
Comments:
0
Category:
Dock
Type:
Bug Report
Use the following code snippet:
ToolTabStrip tabStrip = this.toolWindow1.TabStrip as ToolTabStrip;
this.toolWindow1.Text = "<html><span style=\"font-family:Segoe UI;font-size:8.25;\"><b>Hello</b></span><span" +
" style=\"font-family:Segoe UI;font-size:8.25;\">Woooooooooooooooooorld</span></html>";
TextPrimitive text = tabStrip.CaptionElement.FindDescendant<TextPrimitive>();
text.ClipDrawing = true;
text.StretchHorizontally = false;
text.DisableHTMLRendering = false;
text.AutoEllipsis = false;
Unplanned
Last Updated:
13 Oct 2021 06:40
by ADMIN
Created by:
Arikkan
Comments:
0
Category:
Dock
Type:
Bug Report
Please refer to the attached gif file illustrating better how the non-pinned tabs go behind the pinned tab. This behavior should be prevented and the tabs need to be arranged in a container on the right side of pinned tab.
Unplanned
Last Updated:
24 Dec 2020 11:20
by ADMIN
ADMIN
Created by:
Dimitar
Comments:
2
Category:
Dock
Type:
Bug Report
To reproduce:
See attached video.
Workaround:
public Form1()
{
RadDockEvents.TabStripItemCreating += RadDockEvents_TabStripItemCreating;
InitializeComponent();
radDock1.AutoHideAnimation = Telerik.WinControls.UI.Docking.AutoHideAnimateMode.None;
}
void RadDockEvents_TabStripItemCreating(object sender, TabStripItemCreatingEventArgs args)
{
if (args.AutoHide)
{
var currentScale = args.TabItem.DpiScaleFactor;
Screen showScreen = Screen.FromControl(this);
SizeF scale = NativeMethods.GetMonitorDpi(showScreen, NativeMethods.DpiType.Effective);
if (scale != currentScale)
{
var font = args.TabItem.Font;
var newFont = new Font(font.Name, font.Size * scale.Width, font.Style);
args.TabItem.Font = newFont;
}
}
}
protected override void OnClosed(EventArgs e)
{
RadDockEvents.TabStripItemCreating -= RadDockEvents_TabStripItemCreating;
base.OnClosed(e);
}
Unplanned
Last Updated:
04 Aug 2020 10:46
by ADMIN
Created by:
Henk
Comments:
3
Category:
Dock
Type:
Bug Report
Please run the sample project in an environment with left monitor at 150% DPI scaling and right monitor at 100%. You will notice that the ToolWindow remains with fixed width.
Unplanned
Last Updated:
28 Jul 2020 12:32
by ADMIN
Created by:
대호
Comments:
1
Category:
Dock
Type:
Bug Report
To reproduce:
1. Create a floating window
2. Try to drop another window into the floating window
3. The window is successfully docked into the floating window, but DockStateChanged event does not fire.
Unplanned
Last Updated:
20 Mar 2019 09:44
by ADMIN
ADMIN
Created by:
Dess | Tech Support Engineer, Principal
Comments:
3
Category:
Dock
Type:
Bug Report
To reproduce: please run the attached sample project and follow the steps in the gif file. After some further testing you will notice that the tab items are re-positioned incorrectly when you click a certain tab. It jumps to another location. Workaround: set the MultiLineItemFitMode property to None and specify the DocumentWindow.TabStripItem.Row property in order to arrange the tabs as you wish.
Unplanned
Last Updated:
24 Aug 2018 12:59
by ADMIN
ADMIN
Created by:
Dess | Tech Support Engineer, Principal
Comments:
0
Category:
Dock
Type:
Bug Report
To reproduce: run the application. On the first DocumentWindow there is a UserControl with a wizard. Pressing the Tab key will navigate the command buttons. On the second DocumentWindow there is a similar wizard which is NOT hosted in a UserControl.
Workaround: Currently, you can override the ProcessDialogKey method of RadWizard and handle the Tab key where you can perform the desired logic, e.g. select a specific control:
public class MyWizard : RadWizard
{
protected override bool ProcessDialogKey(Keys keyData)
{
if (keyData == Keys.Tab)
{
WizardPage page = this.SelectedPage;
page.ContentArea.Controls[0].Focus();
return false;
}
return base.ProcessDialogKey(keyData);
}
}
Unplanned
Last Updated:
26 Jun 2018 07:42
by ADMIN
ADMIN
Created by:
Dimitar
Comments:
0
Category:
Dock
Type:
Bug Report
Please use attached project and try the following: 1. Run the application and move toolWindow3 from right to the bottom panel. 2. Hide toolWindow3 by 'Toggle' menu item or just close it. 3. Save the layout pressing 'Save' menu item. 4. Close the application and run it again. 5. Restore layout using 'Init' menu item. 6. Press 'Toggle' menu item to show toolWindow3. Workaround: Make the window visible before loading the layout.
Unplanned
Last Updated:
19 Apr 2018 13:49
by ADMIN
ADMIN
Created by:
Dimitar
Comments:
2
Category:
Dock
Type:
Bug Report
If you drag a regular form to the top of the screen it will be maximized. This should work with the floating window as well.
Unplanned
Last Updated:
06 Mar 2018 09:34
by ADMIN
ADMIN
Created by:
Hristo
Comments:
0
Category:
Dock
Type:
Bug Report
The attached videos demonstrate the present behavior and the desired one
How to reproduce:
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
this.radDock1.EnableFloatingWindowSnapping = true;
DragDropService svc = this.radDock1.GetService<DragDropService>();
svc.DragDropMode = DragDropMode.Preview;
}
}
Unplanned
Last Updated:
06 Dec 2017 09:19
by Froggie
ADMIN
Created by:
Dimitar
Comments:
1
Category:
Dock
Type:
Bug Report
This property should be inherited by all tool, document, floating and autohide windows.
Unplanned
Last Updated:
20 Nov 2017 15:27
by ADMIN
ADMIN
Created by:
Dimitar
Comments:
0
Category:
Dock
Type:
Bug Report
To reproduce:
Open the attached project and press Ctrl+ Tab in the first text box. Since the textboxes are accepting the Tab, Ctrl + Tab should move to the other control.
Workaround
// RadTextBox
private void TextBoxItem_PreviewKeyDown(object sender, PreviewKeyDownEventArgs e)
{
if ((e.KeyData & Keys.Tab) == Keys.Tab && (e.KeyData & Keys.Control) == Keys.Control)
{
e.IsInputKey = true;
var item = sender as RadTextBoxItem;
this.SelectNextControl(item.HostedControl, true, true, true, true);
}
}
//RadTextBoxControl
private void RadTextBoxControl1_PreviewKeyDown(object sender, PreviewKeyDownEventArgs e)
{
if ((e.KeyData & Keys.Tab) == Keys.Tab && (e.KeyData & Keys.Control) == Keys.Control)
{
e.IsInputKey = true;
this.SelectNextControl(sender as RadTextBoxControl, true, true, true, true);
}
}