as magnetic behaviour I mean that when you move a window close to another window, the first window just snap to the other. The same behaviour is fine when you resize a window.
The magnetic behaviour helps you to arrange floating windows into the screen, so people dont get crazy trying to align and resize all the floating windows around in the screen.

I have issues with Databindings for RadToggleButton and RadDock ToolWindow.

Here are 3 scenarios to try with my repro application.

ToggleButton
Click the radToggleButtonElement1, notice that the binding never occurs.

ToolWindow Docking issue 1
Dock the toolWindow1 to the left over ToolWindow2
Click toolWindow2
Click toolWindow1
Click toolWindow2
Notice each time you click another tool window, the binding is triggered even if the property value hasn't changed.

ToolWindow Dockin issue 2
Dock the toolWindow1 to the left over toolWindow2
Notice that the binding is triggered, but with the previous value (Floating instead of Docked)
close the toolWindow1
Notice that the binding is triggered, but with the previous value (Docked instead of Hidden)

There should be a method which allows the user to host a Form in a HostWindow. This will come in handy when there is a save/load layout scenario.

Resolution: 
Use the DockControl method to host a form. Here is the code snippet: 
Form form = new Form8();
this.radDock1.DockControl(form, Telerik.WinControls.UI.Docking.DockPosition.Left);

Currently, it is not possible to add any RadElement to a TabStripItem in DocumentTabStrip.

Resolution: 
Use the static class RadDockEvents to subscribe to events before InitializeComponent

Would be useful to have the option to create the tab close button theme which depends on the states of the button's containing tab.

Hidden HostWindows are not loaded correctly when the load operation is performed twice.

FIX. RadDock - with two nested docks, setting the DocumentTabsAlignment of the other dock automatically sets the same on the inner one and this cannot be changed. Once you change it and reload the design time, its setting is being reset.

To reproduce 
- add RadDock with couple DocumenWindows in it
- add second RadDock with coupld DocumentWindows in it, in one of the windows of the first dock
- set Raddock2 DoumentTabsAlignment to top
- set DocumentTabStrip2 TabStripAlignment also to top or default
- drag a radbutton into documentwindow3 and double click it, to get a click event
- go into code view and remove the created event manually
- change back to form view. the alignment in DocumentTabStrip2 has been automatically changed to bottom

To reproduce:
- Add 2 DockWindows and dock it Add about 10 controls in one of the windows. AutoHide them and show them one after another, you will notice that the old one is visible somewhere in the middle of the animation.
- Also you will notice that AutoHideWindowDisplayed and AutoHideWindowDisplaying events are fired twice.

1. Create a new project with RadDock and add 5 tool windows.
2. Dock all tool windows to bottom.
3. Reset the order of the tool windows to not be 1-5
4. Set the group to auto-hide
5. Save dashboard layout
6. Load dashboard layout

1. Create a project with RadDock.
2. Add several tool windows.
3. Run the project.
4. Auto hide all tool windows at the bottom.
5. Close the last tool window.
6. Save the layout.
7. Load the layout.

This feature request refers to introducing a new ToolWindow property which will allow setting individually text to the ToolWindow's Caption and Tab.

The DocumentTabStrip raises the SelectedIndexChanging event twice

Dock windows should keep its icon and image that is set for them in a previous state, no matter their form, tabbed, docked,

These are the steps to reproduce the bug:

1. Start dragging a docked window tab (but don't leave the tab bounds for now).
2. While still holding the left mouse button, click the right mouse button to let the context menu appear.
3. Now drag the tab outside the tab bar until the window gets undocked (for example to the blue region above the docked windows).
4. Finish dragging by releasing the left mouse button.
5. Move the mouse cursor over the title bar of another docked window -> the window is undocked without interacting with it and will stick to the cursor until you click the mouse button to release it.

Workaround:
   bool flag = false;
        public Form1()
        {
            InitializeComponent();
            
            ContextMenuService menuService = this.radDock1.GetService<ContextMenuService>();
            menuService.ContextMenuDisplaying += menuService_ContextMenuDisplaying;

            DragDropService service = this.radDock1.GetService<DragDropService>();
            service.Starting += service_Starting;
        }

        void service_Starting(object sender, StateServiceStartingEventArgs e)
        {
            e.Cancel = flag;
            flag = false;
        }

        void menuService_ContextMenuDisplaying(object sender, ContextMenuDisplayingEventArgs e)
        {
            flag = true;
        }

To reproduce:
- Add 2 RadFoms to a raddock in mdi mode.
- Dock the windows by using the left or right docking guide in the center.
- You will notice that the behavior is the same as like using the left or right side guides.

To reproduce:
- Add two tool windows and auto hide them, one on the left and on the right
- Then call the AutoHideWindow method like this (ToolWindow1 should be on left side):

RadDock1.AutoHideWindow(ToolWindow1)

- You will notice that the second windows is moved on the left.

Workaround:
Use the DockState property instead of the method.

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.

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;
}

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.

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);
}

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.