-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Question: is it possible to avoid bouncing ? #3
Comments
Our desired behavior is "send me to the nearest place that's ok". |
@shliama It would be great to be able to have the choice of what to use. |
+1 |
Please check version 1.2.0, above issue must be fixed. I've updated core logic so an image must correct its position smoothly and obviously. |
@shliama Seems to work perfectly. |
Will you also consider the other solution? |
No, current behavior is by design. Image cannot be cropped if it does not fill the cropping bounds - so it must be forced to fill em. |
@shliama Well, we could choose which color/background to use for the parts that are not of the cropped area of the bitmap. |
This is how our UCropActivity works. But it's not final - so you are able to extend it and create any behaviour you want. |
@shliama Maybe some day. Currently I'm quite busy. Sorry and thank you for your time. |
if I move the rectangle outside of the bitmap, it sends me back to where I was.
Is it possible to avoid this, and instead have one of these behaviors:
The reason is that it's very hard, for example, to crop the image including the edges.
Same goes for when the image is rotated.
The text was updated successfully, but these errors were encountered: