Thank you for the clarification. With the Q2 release, we introduced support for binding the view events to the view model. This, however has broken your approach where you instantiate a secondary widget on top of the view (due to two widgets and an MVVM bound to the single element).
One way to work around this problem is to move the touch widget to an inner event or to use the listview widget click event. Your scenario would be completely covered by the listview widget click event, eliminating the additional kendoTouch initialization.
Another approach (which is a bit accidental) would be to modify the initialization of the view like this
. However, I would recommend the former.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI