Just for historical purposes I am publishing the conclusion reached in the tracker here.

While preparing the patch for you, today I was testing the behavior in Windows 8 and, surprisingly, it seems that the same problem appears. I am not able to receive the PointerMoved and PointerReleased. The explanation is here:

http://stackoverflow.com/questions/2582 ... -and-touch

As soon as the manipulation starts (the finger is moved) no more touch events appear in the ScrollViewer.

Although the reasons in NoesisGUI are different I think we shouldn't deviate from the Microsoft behavior.

The proposed woraround is disabling the manipulations in the ScrollViewer by setting the property PanningMode to None.

Did this issue get fixed? I'm debugging an issue where I don't get TouchUp events, and I have a ScrollViewer. Wondering if it could be related.

We never fixed this because we had a similar behavior to WPF. Although I am not sure the solution is 100% satisfactory. We are moving to the touch UWP model though, it is in the roadmap. I don't know, could you create a new thread for discussing your problem? Thanks

Thanks for the info! I'll try a workaround here and start a new thread if I don't find one. +1 for the UWP model (with PointerXX)

Thank you!

Just to close on this, since I found a workaround.
I feed the Unity touchdown/move/up events to my own code that uses VisualTreeHelper.HitTest() to determine which control is hit, effectively bypassing Noesis event handling.
Once there is UWP-style handling may try using the PointerXX events.

Could you describe a bit more about your scenario? Maybe we need to revisit this thread in the future.

This is what we have planned for the new architecture: https://trello.com/c/zN2r19h4/260-improve-manipulations

I think the Trello post 1. "Manipulation and Touch events should be handled independently. " summarizes the fix for my scenario.

We have two scenarios:
1. Have a tilt control effect like this video: https://www.youtube.com/watch?v=1z7N4yRxxI0
Controls are inside ScrollViewer. Since touch is handled by the ScrollViewer, manipulations don't trigger on the controls inside.
I haven't opened bug on this one - assuming it's the same as (2.) below and will be fixed with the UWP model or the fix for (2.)

2. Have a button inside ScrollViewer
This one is simple - just add a button in a ScrollViewer and the button's Pressed state is never activated. http://www.noesisengine.com/bugs/view.php?id=1170

Thanks a lot for the clarifications!