The user should be allowed to modify the default behavior of floating windows and decide whether they should be owned by the main Form or they should act like normal Forms - with Minimize/Maximize options and appearing in the System's Taskbar.
It will be nice to have FloatingSize or DefaultFloatingSize property at a DockWindow level. This will allow the user to have a floating window with a custom default size different than 300x300.
There should be mechanism for specifying which windows should be saved by the SaveToXml method. Resolution: You need to subscribe to the DockWindowSerializing event to prevent saving of window. Please refer to the following code example: void radDock1_DockWindowSerializing(object sender, DockWindowCancelEventArgs e) { if (e.NewWindow.Text == "WindowName") { e.Cancel = true; } }
The ShowAutoHidePopup method should enable showing auto hidden pop-ups.
Currently it is not possible to customize the tool window animation and there is no animation when closing the tool window. Resolution: Set the AutoHideAnimation and the AutoHideAnimationDuration properties of RadDock
IMPROVE: RadDock - currently when middle click is executed the ActiveWIndows closes instead of the clicked one
When you add a few DocumentWindows to RadDock and you undock one of them to a floating window, then undock another one in the same floating window you will see two tabs. In the main area the selected tab is bolded, the functionality should be the same in the floating windows For the time being use the following code to manually bold the tabs: this.RadDock.FloatingWindowCreated += RadDock_FloatingWindowCreated; ... void RadDock_FloatingWindowCreated(object sender, FloatingWindowEventArgs e) { e.Window.Controls[0].ControlAdded += Form1_ControlAdded; } void Form1_ControlAdded(object sender, ControlEventArgs e) { DocumentTabStrip tabStrip = e.Control as DocumentTabStrip; tabStrip.ControlAdded -= Form1_ControlAdded; if (tabStrip != null) { tabStrip.SelectedIndexChanged += tabStrip_SelectedIndexChanged; } } void tabStrip_SelectedIndexChanged(object sender, EventArgs e) { DocumentTabStrip tabStrip = sender as DocumentTabStrip; if (tabStrip != null) { foreach (DocumentWindow item in tabStrip.Controls) { item.TabStripItem.ResetValue(RadItem.FontProperty, ValueResetFlags.Local); } tabStrip.SelectedTab.TabStripItem.Font = new Font(tabStrip.SelectedTab.Font.FontFamily, tabStrip.SelectedTab.Font.Size, FontStyle.Bold); } }
http://blogs.msdn.com/b/zainnab/archive/2012/06/19/visual-studio-2012-new-features-preview-tab.aspx
There should be a method which hides/closes (depending on the CloseAction) a DocumentWindow. This method should be called from the DocumentWindow instance.
One should know what is the reason that causes a transaction to take place. For example, if you double-click the titlebar of a FloatingWindow to redock it in RadDock, the user should known that the reason is a double-click operation.
There should be events firing when the AutoHideWindow pops up and collapses.
Currently, no images are shown in AutoHideTabs of ToolWindows. It will be a nice feature if there are such images.
When saving the layout RadDock saves the windows as they appear in the DockWindows collection. However, improvement to save the current toolwindows position will be great addition.
IMPROVE. RadDock - add possibility for replacing the page items in the DocumentWindows with custom ones. Resolution: Use the static class RadDockEvents to subscribe to events before InitializeComponent
Add the ability to easily turn on/off the DockingGuides
Currently auto-hidden windows are displayed under following conditions: - Associated TaItem is hovered or - Associated TabItem is clicked or - The DockWindow itself becomes the currently Active one We should allow the user to control these conditions.
One possible scenario is adding an application menu button like in RadRibbonBar.
This request concerns adding a state for the buttons in the ToolWindow caption, which will allow different theming for the buttons, when the window is active and inactive.