SplitButton does not mark mouse events handled

[bloritsch]

What steps will reproduce this issue?

We have an application that has a canvas that allows users to add elements by mouse click. We had some formatting controls accessible via a SplitButton. When a user opened the drop down, the mouse was also over the canvas. When they selected an option, the mouse click was bubbled through to our canvas and our code attempted to create an element at that position.

Expected outcome

We expected the SplitButton drop down to behave more like a ComboBox. When the user selects an option from the ComboBox, the mouse up event is marked as e.Handled = true. That prevents the erroneous click on the canvas.

Our short term fix for now is to use a ComboBox and a separate button.

Environment

• MahApps.Metro v1.1.2
• Windows 7 pro
• Visual Studio 2013
• .NET Framework 4.5

[punker76]

@bloritsch Please test this again after merged PR #2572 thx!

[punker76]

@bloritsch Could you retest this with latest pre-release?

[bloritsch]

I'm sorry, I haven't gotten back to you yet. I've been so crazy busy with
this software release and then a bunch of busy stuff at home. Hopefully I
will be able to test it tomorrow. Is the fix in a Pre-release or the
official release?

On Thu, Jul 21, 2016 at 3:54 PM, Jan Karger notifications@github.com
wrote:

@bloritsch https://github.com/bloritsch Could you retest this with
latest pre-release?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#2545 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL4DmSuXzyt8gqL6RfOUUa6GijqMp8jks5qX86SgaJpZM4I0TKD
.

[punker76]

@bloritsch np, try latest pre-release, thx.

[bloritsch]

Confirmed. It's working now.