Quantcast
Channel: AvalonDock
Viewing all 2690 articles
Browse latest View live

Created Unassigned: Focusing issue when having floating documents [16251]

$
0
0
When having a floating document which is in focus and clicking on a menu item in the main window (or any other control not in a document or acnhorable) the focus is not set correctly.

Steps to reproduce:

- Run MVVMTestApp
- Open two documents
- Float one of them
- __Click on the "Tools" menu, and it opens correctly.__
- Now, click inside the _docked_ document (focusing its TextBox)
- Click on the floating document
- __Click on the "Tools" menu, and it does not open__ instead focus is set to the TextBox inside the docked document.

Created Unassigned: Metro Theme: Resources missing [16253]

$
0
0
Hey!

Just a small issue in the metro theme: Some Resources can't be found, e.g.

> Resource not found; ResourceKey='AvalonDock_ThemeMetro_BaseColor33'

See MVVM Demo App.

Thanks, micro

Commented Issue: ILayoutUpdateStrategy not working [16050]

$
0
0
Hi all,

I'm using AvalonDock 2.0.1746 with PRISM and in my project I add LayoutAnchorable dynamically. This is my code:

```
public bool BeforeInsertAnchorable(LayoutRoot layout, LayoutAnchorable anchorableToShow,
ILayoutContainer destinationContainer)
{
//AD wants to add the anchorable into destinationContainer
//just for test provide a new anchorablepane
//if the pane is floating let the manager go ahead
var destPane = destinationContainer as LayoutAnchorablePane;
if (destinationContainer != null && destinationContainer.FindParent() != null) return false;

string destPaneName;
if (anchorableToShow.Content is ChartTabView)
destPaneName = "ChartToolsPane";
else if (anchorableToShow.Content is TreeNodesView)
destPaneName = "TreeToolsPane";
else
return false;

var toolsPane = layout.Descendents().OfType().FirstOrDefault(d => d.Name == destPaneName);
if (toolsPane == null) return false;

toolsPane.Children.Add(anchorableToShow);
return true;
}

```
In new version the layout.Descendents() always return null for "ChartToolsPane"(the "TreeToolsPane" I create when programm starts), but in older version it's working fine.

What can I resolve this problem?

Thanks,
Arthur
Comments: ** Comment from web user: ElByte **

Hi,

I know this is not my thread, but I have the same issue and would like to see it resolved, rather then using my work-around. Do you still need a project emartin? I can put one together for you.

In the meantime, you can re-produce this in the following way:
* add at least two panels of one type in xaml In my case I have one document, two docable
* the second docable gets a name, but is empty, as I don't need it at startup
<aDock:LayoutAnchorablePane Name="commonView" DockMinHeight="110" DockHeight="110" >
</aDock:LayoutAnchorablePane>
* Create a LayoutUpdateStrategy
public bool BeforeInsertAnchorable(LayoutRoot layout, LayoutAnchorable anchorableToShow, ILayoutContainer destinationContainer)
{
var destCommonPane = layout.Descendents().OfType<LayoutAnchorablePane>().FirstOrDefault(d => d.Name.Equals("commonView"));
}

* first time around, destCommonPane will be null ! but as far as I can tell, since it is definded in xaml, it should return the panel, like it does with the other
* If you add a dummy control in xaml, and hide it, the pane will be found
* I personally add it via code, in this method as a workaround.

Oh, and I use the MVVM approach, so it's bound to a List

Just let me know if you still need a demo and I put one together

regards


New Post: How to collapse RightSide LayoutAnchorGroup

$
0
0
I have the following xaml which works fine, the RightSide items ProcessExplorer and DataExplorer are UserControls that are TreeViews. The User can pick items on the TreeViews and new LayoutDocuments are added to the mainPanel. In version 1.3 we could collapse the RightSide items after a pick without the user moving the mouse off the TreeView. But in version 2.0 I can not figure out how from the code behind to make that happen.

Note we do not allow the user to mess with the Home Page or the RightSide items. That's why the CanClose, CanFloat, CanHide, CanAutoHide are all set to false. On new pages they can do what they want.
<Window x:Class="TestApp.Shell"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
    xmlns:ad="http://schemas.xceed.com/wpf/xaml/avalondock"
    xmlns:local="clr-namespace:TestApp"
    xmlns:sc="clr-namespace:TestApp.StaticContent"
    Title="TestApp" Width="1024" Height="800"
            Loaded="OnLoaded" IsVisibleChanged="isVisibleChanged" Closing="OnClosing">
<Grid x:Name="ShellRegion">
    <!-- New children, such as the modal dialog box, can be added in the ShellRegion. -->
    <Grid x:Name="DockingRegion">
        <ad:DockingManager x:Name="DockManager" AllowMixedOrientation="True"
            AnchorableContextMenu="{x:Null}">
            <ad:LayoutRoot>
                <ad:LayoutPanel Orientation="Horizontal" x:Name="mainPanel">
                    <ad:LayoutDocumentPaneGroup>
                        <ad:LayoutDocumentPane x:Name="MainWindow">
                            <sc:StartPage Title="Home Page" CanClose="False" CanFloat="False"/>
                    </ad:LayoutDocumentPaneGroup>
                </ad:LayoutPanel>
                <ad:LayoutRoot.RightSide>
                    <ad:LayoutAnchorSide>
                        <ad:LayoutAnchorGroup>
                            </ad:LayoutAnchorable>
                            <ad:LayoutAnchorable Title="Process Explorer" ContentId="processexplorer" x:Name="pxProcessExplorer" 
                                                            AutoHideMinWidth="300"
                                                            CanClose="False" CanFloat="False" CanHide="False" CanAutoHide="False">
                                <sc:ProcessExplorer/>
                            </ad:LayoutAnchorable>
                            <ad:LayoutAnchorable Title="Data Explorer" ContentId="dataexplorer" x:Name="adDataExplorer" 
                                                               AutoHideMinWidth="300"
                                                               CanClose="False" CanFloat="False" CanHide="False" CanAutoHide="False">
                                <sc:DataExplorer/>
                            </ad:LayoutAnchorable>
                        </ad:LayoutAnchorGroup>
                    </ad:LayoutAnchorSide>
                </ad:LayoutRoot.RightSide>
            </ad:LayoutRoot>
        </ad:DockingManager>
    </Grid>
</Grid>

Released: AvalonDock 2.0.1746 (Dec 04, 2012)

$
0
0

Welcome to the release of AvalonDock 2.0

This release contains a lot (lot) of bug fixes and some great improvements:
  • View caching. Content of documents and anchorables are no longer recreated everytime a user moves them.
  • Auto-hide pane now opens quickly.
  • Two new themes. Expression (Dark and Light) and Metro. Both of them still in experimental stage.

Updated Release: AvalonDock 2.0.1746 (Dec 04, 2012)

$
0
0

Welcome to the release of AvalonDock 2.0

This release contains a lot (lot) of bug fixes and some great improvements:
  • View caching. Content of documents and anchorables are no longer recreated everytime a user moves them.
  • Auto-hide pane now opens quickly.
  • Two new themes. Expression (Dark and Light) and Metro. Both of them still in experimental stage.

New Post: [Version 2.0] How to control the layout of a document when adding to the DocumentsSource

$
0
0
I'm binding to the DocumentsSource, and as I add new ViewModel objects to the backing collection the appear as new Documents in the LayoutDocumentPane --- that's the easy part.

In some cases I would like to control how those documents are displayed --- perhaps floating (and when floating at a certain size) and also perhaps docked beside an existing document rather than tabbed over top.

It's completely unclear how to get that level of position control.

I'm also rather disappointed at the lack of documentation --- is the full API documented somewhere else that I'm prehaps missing. All I see here is this

Updated Release: AvalonDock 2.0.2000 (Jun 12, 2013)

$
0
0
Issue 15837 - Floating Window bottom right resize grip size increased.
Resolved in this update

Issue 15781 - 'Loaded' event fired twice on a UserControl inside dock manager
Issue 15753 - Loading the controls twice, parent window null
Discussion 405460 - Deserializing floating window results in two views
Patch 13440 - This patch fixes a problem with floating windows and multi-monitor setups
Issue 15758 - Reloading layout item cannot be cancelled on error
Issue 16194 - Cannot resize panes
Issue 15976 - Focus problem with buttons
Issue 15630 - LayoutDocument Title Property cannot be bound to
Issue 15976 - Focus problems in AutoHideWindow fixed (see comments)
Issue 15234 - CanClose and CanHidedoes not work right on LayoutAnchorable
Issue 1500 - Maximized info not stored in layout

Released: AvalonDock 2.0.2000 (Jun 12, 2013)

$
0
0
Resolved in this update

Issue 15837 - Floating window bottom right resize grip size increased
Issue 15781 - 'Loaded' event fired twice on a UserControl inside dock manager
Issue 15753 - Loading the controls twice, parent window null
Discussion 405460 - Deserializing floating window results in two views
Patch 13440 - This patch fixes a problem with floating windows and multi-monitor setups
Issue 15758 - Reloading layout item cannot be cancelled on error
Issue 16194 - Cannot resize panes
Issue 15976 - Focus problem with buttons
Issue 15630 - LayoutDocument Title Property cannot be bound to
Issue 15976 - Focus problems in AutoHideWindow fixed (see comments)
Issue 15234 - CanClose and CanHidedoes not work right on LayoutAnchorable
Issue 1500 - Maximized info not stored in layout

Updated Release: AvalonDock 2.0.2000 (Jun 12, 2013)

$
0
0
Resolved in this update

Issue 15837 - Floating window bottom right resize grip size increased
Issue 15781 - 'Loaded' event fired twice on a UserControl inside dock manager
Issue 15753 - Loading the controls twice, parent window null
Discussion 405460 - Deserializing floating window results in two views
Patch 13440 - This patch fixes a problem with floating windows and multi-monitor setups
Issue 15758 - Reloading layout item cannot be cancelled on error
Issue 16194 - Cannot resize panes
Issue 15976 - Focus problem with buttons
Issue 15630 - LayoutDocument Title Property cannot be bound to
Issue 15976 - Focus problems in AutoHideWindow fixed (see comments)
Issue 15234 - CanClose and CanHidedoes not work right on LayoutAnchorable
Issue 1500 - Maximized info not stored in layout

Reviewed: AvalonDock 2.0.2000 (Jun 12, 2013)

$
0
0
Rated 4 Stars (out of 5) - Given recent developments (NSA snooping revelations), maybe having an example call PRISM integration might not be the best idea... :)

New Post: [Version 2.0] BindingFailure and FileNotFound first chance exceptions on startup

$
0
0
Hi !

I downloaded this morning the new version (2.0.2000 - changeset 102188).
I updated my source code in order to change the broken "using namespace".

When I launch the debugging session I'm having a BindingFailure exception :
BindingFailure a été détecté
Message: L'assembly avec le nom complet 'Xceed.Wpf.AvalonDock.Aero' n'a pas pu se charger dans le contexte de liaison 'Load' de l'AppDomain ayant l'ID 1.
La cause de l'erreur était : System.IO.FileNotFoundException:
Impossible de charger le fichier ou l'assembly 'Xceed.Wpf.AvalonDock.Aero, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' ou une de ses dépendances.
Le fichier spécifié est introuvable.
Or Google's translation :
BindingFailure was detected
Message: The assembly with the full name 'Xceed.Wpf.AvalonDock.Aero' failed to load in the context of binding 'Load' the AppDomain with ID 1.
The cause of the error was: System.IO.FileNotFoundException:
Could not load file or assembly 'Xceed.Wpf.AvalonDock.Aero, Version = 2.0.0.0, Culture = neutral, PublicKeyToken = 3e4669d2f30244f4' or one of its dependencies.
The specified file was not found.
There is also a bunch on FileNotFoundException :
L'exception System.IO.FileNotFoundException s'est produite
  HResult=-2147024894
  Message=Impossible de charger le fichier ou l'assembly 'Xceed.Wpf.AvalonDock.XmlSerializers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' ou une de ses dépendances. Le fichier spécifié est introuvable.

Xceed.Wpf.AvalonDock.Layout.Serialization.XmlLayoutSerializer.Deserialize(System.IO.TextReader reader) Ligne 77 C#
Xceed.Wpf.AvalonDock.Layout.Serialization.XmlLayoutSerializer.Deserialize(string filepath) Ligne 107    C#
AvalonDock.MVVMTestApp.MainWindow.MainWindow_Loaded(object sender, System.Windows.RoutedEventArgs e) Ligne 62   C#

Xceed.Wpf.AvalonDock.Layout.LayoutGroup<Xceed.Wpf.AvalonDock.Layout.ILayoutPanelElement>.ReadXml(System.Xml.XmlReader reader) Ligne 219 C#
Xceed.Wpf.AvalonDock.Layout.LayoutPositionableGroup<Xceed.Wpf.AvalonDock.Layout.ILayoutPanelElement>.ReadXml(System.Xml.XmlReader reader) Ligne 297 C#
Xceed.Wpf.AvalonDock.Layout.LayoutPanel.ReadXml(System.Xml.XmlReader reader) Ligne 78   C#
The exception only happens if Visual Studio is told to break on first-chance exceptions (Visual Studio top menu -> Debugging -> Exceptions -> select all or only BindingFailure and FileNotFound)

In order to check if my code was causing the exception, I downloaded the AvalonDock source code and I'm having the same issue after customizing the "break on first chance exceptions" settings.

Not a critical issue but as I launch my debugging sessions with all first-chance exceptions enabled, it is quite annoying ! :)

Created Unassigned: [Version 2.0] BindingFailure and FileNotFound first chance exceptions on startup [16261]

$
0
0
Hi !

I downloaded this morning the new version (2.0.2000 - changeset 102188).
I updated my source code in order to change the broken "using namespace".

When I launch the debugging session I'm having a BindingFailure exception :
```
BindingFailure a été détecté
Message: L'assembly avec le nom complet 'Xceed.Wpf.AvalonDock.Aero' n'a pas pu se charger dans le contexte de liaison 'Load' de l'AppDomain ayant l'ID 1.
La cause de l'erreur était : System.IO.FileNotFoundException:
Impossible de charger le fichier ou l'assembly 'Xceed.Wpf.AvalonDock.Aero, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' ou une de ses dépendances.
Le fichier spécifié est introuvable.
```

Or Google's translation :
```
BindingFailure was detected
Message: The assembly with the full name 'Xceed.Wpf.AvalonDock.Aero' failed to load in the context of binding 'Load' the AppDomain with ID 1.
The cause of the error was: System.IO.FileNotFoundException:
Could not load file or assembly 'Xceed.Wpf.AvalonDock.Aero, Version = 2.0.0.0, Culture = neutral, PublicKeyToken = 3e4669d2f30244f4' or one of its dependencies.
The specified file was not found.
```

There is also a bunch on FileNotFoundException :
```
L'exception System.IO.FileNotFoundException s'est produite
HResult=-2147024894
Message=Impossible de charger le fichier ou l'assembly 'Xceed.Wpf.AvalonDock.XmlSerializers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e4669d2f30244f4' ou une de ses dépendances. Le fichier spécifié est introuvable.

Xceed.Wpf.AvalonDock.Layout.Serialization.XmlLayoutSerializer.Deserialize(System.IO.TextReader reader) Ligne 77 C#
Xceed.Wpf.AvalonDock.Layout.Serialization.XmlLayoutSerializer.Deserialize(string filepath) Ligne 107 C#
AvalonDock.MVVMTestApp.MainWindow.MainWindow_Loaded(object sender, System.Windows.RoutedEventArgs e) Ligne 62 C#

Xceed.Wpf.AvalonDock.Layout.LayoutGroup<Xceed.Wpf.AvalonDock.Layout.ILayoutPanelElement>.ReadXml(System.Xml.XmlReader reader) Ligne 219 C#
Xceed.Wpf.AvalonDock.Layout.LayoutPositionableGroup<Xceed.Wpf.AvalonDock.Layout.ILayoutPanelElement>.ReadXml(System.Xml.XmlReader reader) Ligne 297 C#
Xceed.Wpf.AvalonDock.Layout.LayoutPanel.ReadXml(System.Xml.XmlReader reader) Ligne 78 C#
```

The exception only happens if Visual Studio is told to break on first-chance exceptions (Visual Studio top menu -> Debugging -> Exceptions -> select all or only BindingFailure and FileNotFound)

In order to check if my code was causing the exception, I downloaded the AvalonDock source code and I'm having the same issue after customizing the "break on first chance exceptions" settings.

Not a critical issue but as I launch my debugging sessions with all first-chance exceptions enabled, it is quite annoying ! :)

Updated Wiki: Version2Concept

$
0
0

Version 2.0

AvalonDock 2.0 has been rewritten from scratch using an MVVM approach. There is a deep separation between the Model (that describes how the layout is composed), the ViewModel (which prepares the model to be consumed by the view) and the View (a set of stylizable controls that show the user controls).

We've put a lot of attention to WPF Logical/Visual tree management. There is one and only one logical tree which has DockingManager as root. Even if a control is placed in a different window (auto-hide or floating), it always belongs to the same logical tree, below DockingManager.

Binding Issues fixed
Version 1.* suffered from of an annoying issue regarding binding that didn't work for flyout panes and floating windows. The problem here is that WPF's logical tree breaks when content is moved inside another window, such as when a user moves a pane in a floating window.
Version 2.0 fixes this problem definitively. For a detailed description of the problem please read Binding Issues.

MVVM support added
Using an MVVM approach with version 1.* was quite a challenge (you can find a great tutorial at http://www.codeproject.com/KB/WPF/AvalonDockMVVM.aspx). Version 2.0 supports MVVM natively because you can create your model and using DockingManager as the view.

Flyout windows perfomance improved
In version 1.* when a user put content in autohide state, a new window was created by AvalonDock. The window's position and size had to be kept in sync with the docking manager. This lead to a performance issue due to a lot of framework interop calls. Version 2.0 uses the same mechanism as Visual Studio 2010, child windows with redirected logical trees, to show autohide windows. This provides increased perfomance and stability. For more info please see http://blogs.msdn.com/b/visualstudio/archive/2010/03/23/wpf-in-visual-studio-part-5-window-management.aspx.

Floating windows Aero Snap support added
Version 2.0 supports 'Aero Snap'. For details please see (http://blogs.msdn.com/b/visualstudio/archive/2009/11/05/tips-and-tricks-window-management-aero-snapping.aspx).

Floating windows integrated docking
Version 2.0 lets users redock dockable content inside a floating window, similar to the feature in VS 2010.

Focus and activation
We're working to mitigate/eliminate all the focus/activation problems that caused a lot of headaches when using AvalonDock versions prior to v2.0. This work has not yet been completed. We are contemplating using this technique to accomplish that: http://blogs.msdn.com/b/visualstudio/archive/2010/03/09/wpf-in-visual-studio-2010-part-3-focus-and-activation.aspx

Layout serialization
Version 2.0 layout serialization/deserialization is much easier because layout is now also a model completely separated from the view. This allows for easier integration with frameworks like PRISM/MEF.

WPF standard controls
In version 2.0 I've decided to use WPF standard controls, for example instead of creating a complex panel control I've used the standard grid panel. Using this approach I've reduced the number of classes/code to test and debug and the size of the resulting library.

Updated Wiki: Version2Concept

$
0
0

Version 2.0

AvalonDock 2.0 has been rewritten from scratch using an MVVM approach. There is a deep separation between the Model (that describes how the layout is composed), the ViewModel (which prepares the model to be consumed by the view) and the View (a set of stylizable controls that show the user controls).

We've put a lot of attention to WPF Logical/Visual tree management. There is one and only one logical tree which has DockingManager as root. Even if a control is placed in a different window (auto-hide or floating), it always belongs to the same logical tree, below DockingManager.

Binding Issues fixed
Version 1.* suffered from of an annoying issue regarding binding that didn't work for flyout panes and floating windows. The problem here is that WPF's logical tree breaks when content is moved inside another window, such as when a user moves a pane in a floating window.
Version 2.0 fixes this problem definitively. For a detailed description of the problem please read Binding Issues.

MVVM support added
Using an MVVM approach with version 1.* was quite a challenge (you can find a great tutorial at http://www.codeproject.com/KB/WPF/AvalonDockMVVM.aspx). Version 2.0 supports MVVM natively because you can create your model and using DockingManager as the view.

Flyout windows perfomance improved
In version 1.* when a user put content in autohide state, a new window was created by AvalonDock. The window's position and size had to be kept in sync with the docking manager. This lead to a performance issue due to a lot of framework interop calls. Version 2.0 uses the same mechanism as Visual Studio 2010, child windows with redirected logical trees, to show autohide windows. This provides increased perfomance and stability. For more info please see http://blogs.msdn.com/b/visualstudio/archive/2010/03/23/wpf-in-visual-studio-part-5-window-management.aspx.

Floating windows Aero Snap support added
Version 2.0 supports 'Aero Snap'. For details please see (http://blogs.msdn.com/b/visualstudio/archive/2009/11/05/tips-and-tricks-window-management-aero-snapping.aspx).

Floating windows integrated docking
Version 2.0 lets users redock dockable content inside a floating window, similar to the feature in VS 2010.

Focus and activation
We're working to mitigate/eliminate all the focus/activation problems that caused a lot of headaches when using AvalonDock versions prior to v2.0. This work has not yet been completed. We are contemplating using this technique to accomplish that: http://blogs.msdn.com/b/visualstudio/archive/2010/03/09/wpf-in-visual-studio-2010-part-3-focus-and-activation.aspx

Layout serialization
Version 2.0 layout serialization/deserialization is much easier because layout is now also a model completely separated from the view. This allows for easier integration with frameworks like PRISM/MEF.

WPF standard controls
Version 2.0 makes use of standard WPF control. For example, instead of creating a complex panel control, AvalonDock now uses standard grid panel. Using this approach reduced the number of classes to test and debug and the size of the resulting library.

Updated Wiki: Version2Concept

$
0
0

What's new in version 2.0

AvalonDock 2.0 has been rewritten from scratch using an MVVM approach. There is a deep separation between the Model (that describes how the layout is composed), the ViewModel (which prepares the model to be consumed by the view) and the View (a set of stylizable controls that show the user controls).

We've put a lot of attention to WPF Logical/Visual tree management. There is one and only one logical tree which has DockingManager as root. Even if a control is placed in a different window (auto-hide or floating), it always belongs to the same logical tree, below DockingManager.

Binding Issues fixed
Version 1.* suffered from of an annoying issue regarding binding that didn't work for flyout panes and floating windows. The problem here is that WPF's logical tree breaks when content is moved inside another window, such as when a user moves a pane in a floating window.
Version 2.0 fixes this problem definitively. For a detailed description of the problem please read Binding Issues.

MVVM support added
Using an MVVM approach with version 1.* was quite a challenge (you can find a great tutorial at http://www.codeproject.com/KB/WPF/AvalonDockMVVM.aspx). Version 2.0 supports MVVM natively because you can create your model and using DockingManager as the view.

Flyout windows perfomance improved
In version 1.* when a user put content in autohide state, a new window was created by AvalonDock. The window's position and size had to be kept in sync with the docking manager. This lead to a performance issue due to a lot of framework interop calls. Version 2.0 uses the same mechanism as Visual Studio 2010, child windows with redirected logical trees, to show autohide windows. This provides increased perfomance and stability. For more info please see http://blogs.msdn.com/b/visualstudio/archive/2010/03/23/wpf-in-visual-studio-part-5-window-management.aspx.

Floating windows Aero Snap support added
Version 2.0 supports 'Aero Snap'. For details please see (http://blogs.msdn.com/b/visualstudio/archive/2009/11/05/tips-and-tricks-window-management-aero-snapping.aspx).

Floating windows integrated docking
Version 2.0 lets users redock dockable content inside a floating window, similar to the feature in VS 2010.

Focus and activation
We're working to mitigate/eliminate all the focus/activation problems that caused a lot of headaches when using AvalonDock versions prior to v2.0. This work has not yet been completed. We are contemplating using this technique to accomplish that: http://blogs.msdn.com/b/visualstudio/archive/2010/03/09/wpf-in-visual-studio-2010-part-3-focus-and-activation.aspx

Layout serialization
Version 2.0 layout serialization/deserialization is much easier because layout is now also a model completely separated from the view. This allows for easier integration with frameworks like PRISM/MEF.

WPF standard controls
Version 2.0 makes use of standard WPF control. For example, instead of creating a complex panel control, AvalonDock now uses standard grid panel. Using this approach reduced the number of classes to test and debug and the size of the resulting library.

Updated Wiki: Home

$
0
0

AVALONDOCK

AvalonDock is a docking windows control for WPF that lets you create customizable layouts using a full featured window docking system similar to

what is found in many popular integrated development environements (IDEs) such as Visual Studio. It includes themes and samples to get you

started.

You can get AvalonDock as part of the free open source Extended WPF Toolkit, as part of Xceed Extended

WPF Toolkit Plus
, or you can download a stand-alone version here.

Features
  • Supports MVVM
  • Everything can be restyled
  • Includes popular themes

Latest News

Support Future Development

Please strongly consider getting Extended WPF Toolkit Plus which provides AvalonDock as well as 50+ other awesome WPF controls.

Screenshots

Avalondock.png

Updated Wiki: Home

$
0
0

AVALONDOCK

AvalonDock is a docking windows control for WPF that lets you create customizable layouts using a full featured window docking system similar to what is found in many popular integrated development environements (IDEs) such as Visual Studio. It includes themes and samples to get you started.

You can get AvalonDock as part of the free open source Extended WPF Toolkit, as part of Xceed Extended WPF Toolkit Plus, or you can download a stand-alone version here.

Features
  • Supports MVVM
  • Everything can be restyled
  • Includes popular themes

Latest News

Support Future Development

Please strongly consider getting Extended WPF Toolkit Plus which provides AvalonDock as well as 50+ other awesome WPF controls at the the industry's most affordable price.

Screenshots

Avalondock.png

Updated Wiki: Home

$
0
0

AVALONDOCK

AvalonDock is a docking windows control for WPF that lets you create customizable layouts using a full featured window docking system similar to what is found in many popular integrated development environements (IDEs) such as Visual Studio. It includes themes and samples to get you started.

You can get AvalonDock as part of the free open source Extended WPF Toolkit, as part of Xceed Extended WPF Toolkit Plus, or you can download a stand-alone version here.

Features

  • Supports MVVM
  • Everything can be restyled
  • Includes popular themes

Latest News

Support Future Development

Please strongly consider getting Extended WPF Toolkit Plus which provides AvalonDock as well as 50+ other awesome WPF controls at the the industry's most affordable price.

Screenshots

Avalondock.png

Updated Wiki: Home

$
0
0

AVALONDOCK

AvalonDock is a docking windows control for WPF that lets you create customizable layouts using a full featured window docking system similar to what is found in many popular integrated development environements (IDEs) such as Visual Studio. It includes themes and samples to get you started.

You can get AvalonDock as part of the free open source Extended WPF Toolkit, as part of Xceed Extended WPF Toolkit Plus, or you can download a stand-alone version here.

Features

  • Supports MVVM
  • Everything can be restyled
  • Includes popular themes

Latest News

Support Future Development

Please strongly consider getting Extended WPF Toolkit Plus which provides AvalonDock as well as 50+ other awesome WPF controls at the the industry's most affordable price.

Screenshots

Avalondock.png

Action items

  • Enjoy WPF!
  • Please rate this release and write something positive. It's at the bottom of the downloads page
  • Follow this project (click "follow" at the top right of this page)
  • Follow @datagrid on Twitter for WPF and Toolkit news
  • Like Xceed's WPF page on Facebook
  • Check out a video or two on XceedVideos YouTube Channel
  • Add bugs or feature requests to the Issue Tracker

community-full.png
Viewing all 2690 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>