-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
FlipView SelectionChanged event firing twice since 2.4.0 #4012
Comments
punker76
added a commit
that referenced
this issue
Feb 27, 2021
The SelectionChanged event is a bubbling event, so if the ListBox inside the FlipView fires the event, all other events in the same container will be fired.
punker76
added a commit
that referenced
this issue
Feb 27, 2021
Fix FlipView SelectionChanged event firing twice
punker76
added a commit
that referenced
this issue
Feb 28, 2021
batzen
pushed a commit
to batzen/MahApps.Metro
that referenced
this issue
Mar 3, 2021
The SelectionChanged event is a bubbling event, so if the ListBox inside the FlipView fires the event, all other events in the same container will be fired.
batzen
pushed a commit
to batzen/MahApps.Metro
that referenced
this issue
Mar 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Since MahApps.Metro 2.4.0, the FlipView SelectionChanged event is firing twice. 2.3.4 is only doing this once. I have a long running task in that event and this issue is causing problems.
Steps to reproduce
Expected behavior
The SelectionChanged event should only fire once for FlipView.
Actual behavior
From what I can tell, 2.3.4 is firing the event just for the FlipView while changes in 2.4.0 make it so the event is also triggered for the underlying ListBox control. I was looking at the OriginalSource on the SelectionChangedEventArgs. I tried setting e.Handled = true in my event, but that didn't prevent it from triggering a second time.
Environment
Screenshots
N/A
The text was updated successfully, but these errors were encountered: