Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(GH-3859) Allow own ViewModel collection for HamburgerMenu ItemsSource #3860

Merged
merged 1 commit into from Jun 17, 2020

Conversation

punker76
Copy link
Member

Describe the changes you have made to improve this project

Introduce HamburgerMenuListBox class which handles the IsVisible (IHamburgerMenuItemBase) and IsEnabled (IHamburgerMenuItem) properties and bind them to the properties of the ListBoxItem.

This makes it easier to use own ViewModel collections which are mostly not implement these properties. But now it can be done with the interfaces.

Additional context

Here is an example for this scenario:

mahapps_hamburger_binding

Closed Issues

Closes #3859

Introduce HamburgerMenuListBox class which handles the IsVisible (IHamburgerMenuItemBase) and IsEnabled (IHamburgerMenuItem) properties and bind them to the properties of the ListBoxItem.

This makes it easier to use own ViewModel collections which are mostly not implement these properties. But now it can be done with the interfaces.
@punker76 punker76 added this to the 2.1.0 milestone Jun 17, 2020
@punker76 punker76 merged commit 0117888 into develop Jun 17, 2020
@punker76 punker76 deleted the fix/GH-3859-HamburgerMenu-OwnViewModelCollection branch June 17, 2020 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

HamburgerMenu with own ViewModel collection produces System.Windows.Data Warning and Error
1 participant