You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see mouse events are passed to the underlying Android TextureView, right (haven't tried it myself)?
Do you believe it would be possible to convert QTouchEvent to Android MoveEvent too?
Imagine use case: Sygic can create MapView with type of android.view.TextureView. So we instantiate Sygic navigation via JNI, get TextureView, pass it to the QQuickAndroidOffscreenView, and get "QtQuick-native" navigation component that fits based on Sygic..?
Or maybe QTouchEvent would loose information, or provide some latency, making touch unusable?
Thanks!
The text was updated successfully, but these errors were encountered:
I see mouse events are passed to the underlying Android
TextureView
, right (haven't tried it myself)?Do you believe it would be possible to convert
QTouchEvent
to AndroidMoveEvent
too?Imagine use case: Sygic can create MapView with type of android.view.TextureView. So we instantiate Sygic navigation via JNI, get
TextureView
, pass it to theQQuickAndroidOffscreenView
, and get "QtQuick-native" navigation component that fits based on Sygic..?Or maybe
QTouchEvent
would loose information, or provide some latency, making touch unusable?Thanks!
The text was updated successfully, but these errors were encountered: