![]() Using a view-model is the way it is intended to be used, so this is what we will be looking at. This is similar to other WPF controls such as TreeView where you can also get by without a view-model. It is possible, though I don't recommend it, to use NetworkView programmatically or in XAML without a view-model. NetworkView is intended to be backed with an application-specific view-model. Instead, where appropriate, I'll refer back to previous articles. I won't be covering these techniques in detail here. NetworkView and the sample applications make use of all these techniques. In previous articles I have covered a number of WPF techniques: use of adorners, zooming and panning, binding to UI element positions and most recently drag-selection of multiple items. This will be useful if you want to make your own modifications to NetworkView or if you want to understand my approach to developing a complex WPF custom control.Īt the end of the article is a reference section that describes the public properties, methods and commands exposed by NetworkView. Part 2 goes into detail on the implementation. This part and the reference section are enough if you just want to use NetworkView. Part 1 examines NetworkView usage with walkthroughs of the two sample projects. This article is arranged in two main parts. The article and the sample code show how to use the control from XAML and from C# code. NetworkView, as I have called it, was inspired by and has many similarities to standard WPF controls such as ItemsControl and TreeView. This article examines the use and implementation of a WPF custom control that is used to display and edit networks, graphs and flow-charts. ![]()
0 Comments
Leave a Reply. |