Hi,

We've been analyzing the Behavior in NoesisGUI and it matches exactly what WPF does. Let me try to explain what is happening:

When touch events are used inside a control that handles manipulation (as ScrollViewer does when PanningMode != None), then it captures touch events (raising ManipulationStarting event) until you move or release the touch.

OPTION 1: COMPLETED MANIPULATION

If touch is moved enough, then a manipulation starts (raising ManipulationStarted event, and subsequent ManipulationDelta events). Until touch is released (possibly raising ManipulationInertiaStarting event followed by some more ManipulationDelta events, and finally the ManipulationCompleted event).

This scenario can be better understood with the following MSDN image:
https://i-msdn.sec.s-msft.com/dynimg/IC392642.jpeg

OPTION 2: CANCELLED MANIPULATION

If you release the touch without moving it, then manipulation is cancelled, and previous touch events are promoted to mouse events. That means that the button will receive MouseDown, MouseMove and MouseUp events all in the same frame. So no visible change is seen in the button, but the Click event is always raised.

In a future release we want to change this behavior to something similar to UWP, that is better prepared for touch and multitouch environments than WPF.

Meanwhile, if you want to see a visual response when a Button receives a touch, maybe you can add an EventTrigger for the TouchDown event that animates the backgrounds color:

...

<ControlTemplate.Triggers>

<EventTrigger RoutedEvent="UIElement.TouchDown">

<BeginStoryboard>

<Storyboard>

<ObjectAnimationUsingKeyFrames

Storyboard.TargetProperty="Fill"

Storyboard.TargetName="ButtonBackground">

<DiscreteObjectKeyFrame KeyTime="0" Value="{StaticResource PhoneAccentBrush}"/>

<DiscreteObjectKeyFrame KeyTime="0:0:0.5" Value="{x:Null}"/>

</ObjectAnimationUsingKeyFrames>

</Storyboard>

</BeginStoryboard>

</EventTrigger>

</ControlTemplate.Triggers>

...

Hope this helps.

This is the plan we have to improve Touching in 1.3 (basically, doing in like UWP)

https://trello.com/c/zN2r19h4/260-improve-manipulations

Thanks, sounds good! Given that multitouch is a huge part of the market (phones, tablets) it's important and welcome change.
Thanks for the workarounds!