Here, Twenty20TeamsViewModel is passed as a parameter to the constructor of the sample window. MenuSampleWindow sampleWindow = new MenuSampleWindow(viewModel) public MenuItemViewModel ParentViewModel / /// Gets or sets the parent view model. _header = value NotifyOnPropert圜hanged( " Header") public ObservableCollection ChildMenuItems
Private ObservableCollection _childMenuItems _childMenuItems = new ObservableCollection() Public MenuItemViewModel(MenuItemViewModel parentViewModel) / /// Initializes a new instance of the /// class. The Propert圜hanged event notifies the UI about the changes happening to the property in the View Model.Ĭopy Code public class MenuItemViewModel : BaseViewModel Let’s have a look at the Project structure that I have maintained:Ī BaseViewModel class is maintained which has the implementation for INotifyPropert圜hanged interface which enables to have the Propert圜hanged. Header of the Menu Item is bound to the mapping property in the View Model which is mapped to let's same a Name property in the model. So what a View Model object generally encloses is the state of the model and the properties associated with the presentation layer like IsEnabled, Icon etc. Realizing a Menu Item as a View Model makes the implementation far easier and also enables separation of concern. What I have tried to achieve is to reuse the implementation of Treeview that Josh had done on WPF menus. If you have not gone through the article, please have a look as it is a must read for all MVVM aspirants. It opened at least my eyes and made me realize that a monster like a Treeview in WPF can be easily overwhelmed using a ViewModel approach. This article is inspired from the works of Josh Smith, mainly his implementation of the TreeView. This article is an attempt to visualize a WPF menu using the MVVM architecture.
0 kommentar(er)
