-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable background touch events, until images gets settled to its original position. #5
Comments
@oblador |
Facing the same issue. I have used the Pinchable component like the example below:
Issue screen record given below 20211101_190841.mp4From the moment the issue happens, the image will be present there even after navigating to other pages. Only by closing the app completely the image is dismissed. |
Yeah same |
@oblador kindly reply! |
@Dein1 ?? |
@oblador is there any updates? is there any possibility to get a prop to know if pinch is happening, so we can disable the scroll looking into it, or something like that |
@oblador ? |
Same issue here! |
Are you using the library with something like I am using it, and that issue happen just if I move |
Hello, can you show simple example? |
Has there been any progress on this issue? |
When the animation start I am trying to turn off the user interactions on the activity with: It works good in most cases but when I keep just one finger it starts to move things from the activity that should be blocked, I am trying to check what is going on |
This patch fix the issue:
This is the entire PinchableView.java File:
I will create a pr when I have some time |
This pr fix the issue: |
Great library !
It would be great if background touch/scroll etc.. events can be stopped until image gets settled down to its original position.
Because in few case I have found that user tries to scroll away fast (till that time image was not settled properly to its actual position) and since the actual position of that image gets lost, that image get stuck on the screen. Then user needs to restart the app.
Note : I also confirm this issue exists on android
The text was updated successfully, but these errors were encountered: