Unplanned
Last Updated: 28 Jul 2020 12:32 by ADMIN

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.

Completed
Last Updated: 14 Sep 2020 12:47 by ADMIN
Release R3 2020

Hi, 

I am trying to make a Winforms app high dpi aware. All seems fine except when using a toolwindow on a raddock. Is there some special to setup when I want a Raddock to also autoscale?

I created a GIF to example the behaviour. The left side is at 15% and the right side just at 100%. I move the form from right to left and back. As you can see most controls get resized, except for the size of the toolwindows in the raddock.

The raddock is the only dock on the form and is set to dock in parrent. 

 

At the end of the gif you can see some behaviour when I place the form over both screens. Then the applications breaks. I get this error:

System.ComponentModel.Win32Exception
  HResult=0x80004005
  Message=Fout bij het maken van de vensterkoppeling. (Translation: Error making window link.)
  Source=System.Windows.Forms
  StackTrace:
   at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
   at System.Windows.Forms.Timer.TimerNativeWindow.EnsureHandle()
   at System.Windows.Forms.Timer.TimerNativeWindow.StartTimer(Int32 interval)
   at System.Windows.Forms.Timer.set_Enabled(Boolean value)
   at System.Windows.Forms.Timer.Start()
   at Telerik.WinControls.UI.RadFormControlBase.ScaleControl(SizeF factor, BoundsSpecified specified)
   at System.Windows.Forms.Control.ScaleControl(SizeF includedFactor, SizeF excludedFactor, Control requestingControl)
   at System.Windows.Forms.Control.Scale(SizeF factor)
   at Telerik.WinControls.UI.RadFormControlBase.HandleDpiChanged()
   at Telerik.WinControls.UI.RadFormControlBase.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

Maybe this is normal behaviour, but I still want to mention it, because it is possible that in an work environment, someone might to this from time to time. Maybe not on purpose, but still.

Regariding the high DPI, am I doing something wrong?

Thx.

Henk

 

Completed
Last Updated: 04 Feb 2021 13:56 by ADMIN
Release R1 2021 SP1
Please refer to the attached gif file illustrating better the missing docking guides.
Duplicated
Last Updated: 10 Jun 2021 13:29 by ADMIN

Hi,

I have C# Winforms application targeting .Net 5.

I am trying to use the Raddock with the Visual Studio 2012 dark theme, adding to a radribbonform

There are several tool windows that i have tabbed using the Advance layout designer. When i try to select a tab in the main Visual studio designer i am unable to change it from the one i selected in the Advanced layout designer.

I am also unable to resize the windows using the split container while in standard design view.

I have attached a word document to try and explain.

My VS version is:

 

Microsoft Visual Studio Professional 2019

Version 16.9.1

thanks

Mark.

Unplanned
Last Updated: 13 Oct 2021 06:40 by ADMIN
Created by: Arikkan
Comments: 0
Category: Dock
Type: Bug Report
0
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: 02 Feb 2022 12:27 by ADMIN

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: 16 Sep 2022 07:07 by Ark Technologies
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.
Completed
Last Updated: 18 Jul 2023 14:26 by ADMIN
Release R2 2023 SP1
Currently, loading the store layout in RadDock may result in different UI panels according to the available internal splitcontainers/panels that are invisible. Perhaps a "SaveAsDefaultLayout()" and "RestoreDefaultLayout()" method could be introduced. Thus, it wouldn't be necessary to clear the windows before loading XML layout.
Completed
Last Updated: 07 Aug 2024 15:13 by ADMIN
Release 2024.3.806 (2024 Q3)
The ToolStrip inside the AutoHidePopup is not disposed
Unplanned
Last Updated: 30 Sep 2024 11:28 by ADMIN

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.