Resolved the DrawingView IOS issues in SfTabView. #270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Root Cause of the Issue
The SfTabView's internal gesture handling interferes with the DrawingView's touch processing. Specifically, the tab view's gesture recognizer prematurely cancels the touch event, causing the DrawingView to interpret the interaction as cancelled rather than completed. This happens because the tab view's gesture listener (ITapGestureListener) does not differentiate between general views and specialized touch-sensitive views like DrawingView.
Description of Change
Added a type check in the ShouldHandleTap method of SfTabView's horizontal content iOS class to detect if the touched view is a MauiDrawingView. If so, the tab view disables its own touch processing to allow the DrawingView to handle the gesture correctly.
Issues Fixed
Issue : #258