I can only assume that your Interaction.Triggers
are causing your problem. I accept that you want to 'convert' that event into a Command
, but if you implement a standard MouseDoubleClick
handler instead (just temporarily), you will see that scrolling does not fire the handler at all.
You can still convert that event to a Command
in your own custom Attached Property
. They are relatively simple to create and you can find out how to do this from the Attached Properties Overview page at MSDN.