-
Notifications
You must be signed in to change notification settings - Fork 77
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
images are overwritten without confirmation after rotation and back button #241
Comments
Still affects 1.2.0 release, on LineageOS 21 on Pixel 3 |
The relevant code is in This comes from SimpleGallery times. Original creator was very insistent on implicit rotation save being the correct behavior. |
@rkolbaskin You can create a PR with this change. This bug doesn't have |
@Aga-C My whole experience with kotlin (or java for that matter) is removing those 6 lines of code. I don't even remember how I managed to find out what part of the code to edit and I am not sure what side effects it might have. I don't think I am qualified to make such pull requests. |
Actually no. I do remember. I found implicit save added in commit 18277c1 commented with "save rotated images automatically". |
We're not Simple Mobile Tools - if needed, we can change something done by the original maintainer, even if it was done purposefully. It makes more sense to accept changes with the tick button. |
Checklist
Affected app version
1.1.3
Affected Android/Custom ROM version
Android 13
Affected device model
Motorola Edge 30
How did you install the app?
GitHub releases
Steps to reproduce the bug
Expected behavior
nothing should happen to the image, because the confirmation button wasn't pressed
Actual behavior
the image is re-saved rotated, overwriting the original image, without prompt
Screenshots/Screen recordings
The thumbnail is not updated, but the actual image is now rotated.
Don't check the image with Google Photos because it caches images... use another viewer or check the image checksum before and after the rotation
Additional information
No response
The text was updated successfully, but these errors were encountered: