I've noticed a significant delay (approx. 300ms) when tapping on interactive widgets inside the InteractiveViewer2 when doubleTapToZoom is true (default).
Problem: The current implementation seemingly waits to confirm a gesture is not a double-tap before allowing the single-tap to pass to the child. This creates a "sluggish" feel for every interaction within the viewer.
Proposed Solution / Feature Request: Could we add a flag or behavior mode (e.g., optimisticSingleTap: true or waitForDoubleTap: false) that allows tap events to propagate to the child immediately?
I understand this means a double-tap action would strictly trigger:
Child Tap (Immediate)
Child Tap (Immediate)
Zoom Action
For many use cases (like a canvas editor or map), triggering the child's "select" action underneath the zoom is an acceptable trade-off to gain zero-latency responsiveness. The current forced delay makes the UI feel unresponsive.
Current Workaround: We are forced to disable doubleTapToZoom: false to get acceptable performance, losing the double tap zooming feature entirely.
Context: This is critical for Pro app experiences where users expect instant selection feedback but also want standard zoom semantics.
I've noticed a significant delay (approx. 300ms) when tapping on interactive widgets inside the
InteractiveViewer2whendoubleTapToZoomis true (default).Problem: The current implementation seemingly waits to confirm a gesture is not a double-tap before allowing the single-tap to pass to the child. This creates a "sluggish" feel for every interaction within the viewer.
Proposed Solution / Feature Request: Could we add a flag or behavior mode (e.g., optimisticSingleTap: true or waitForDoubleTap: false) that allows tap events to propagate to the child immediately?
I understand this means a double-tap action would strictly trigger:
Child Tap (Immediate)
Child Tap (Immediate)
Zoom Action
For many use cases (like a canvas editor or map), triggering the child's "select" action underneath the zoom is an acceptable trade-off to gain zero-latency responsiveness. The current forced delay makes the UI feel unresponsive.
Current Workaround: We are forced to disable doubleTapToZoom: false to get acceptable performance, losing the double tap zooming feature entirely.
Context: This is critical for Pro app experiences where users expect instant selection feedback but also want standard zoom semantics.