Photo sketching: UNDO on the second photo shows the first photo
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 64/100
Research direction
Reproduce the four steps from the issue (two photos, sketch the first, save, sketch the second, press UNDO). Locate the sketching/undo implementation for the photo viewer in this Qt/C++ app and inspect how the undo stack is keyed — it likely stores or restores canvas state without being reset when the displayed photo changes. Done means UNDO on the second photo keeps that photo on screen while still removing only its sketches; verify against the recorded video and add a regression test if the project has one for this screen.
Written by the indexing model from the issue text.
Description
Description
If you save sketches on one photo and then press UNDO while sketching on a second photo, the app shows the first photo. UNDO still removes the second photo's sketches, but the second photo is no longer the one on screen.
Environment
Staging
Application (+ app version, build, operating system)
Device: Samsung Galaxy A 53
OS: Android 15
App build: 2026.5.0 - 868151
Steps to reproduce
- Open a feature form that has at least two photos.
- Open the first photo, add sketches and save.
- Open the second photo and add sketches.
- Press UNDO several times.
Actual results
While you press UNDO, the first photo is displayed instead of the second. UNDO removes the second photo's sketches.
Expected results
The second photo stays visible the whole time, and UNDO removes only its sketches.
Frequency: [Intermittent]
Attachments: [screen recording]
https://github.com/user-attachments/assets/a7c43284-7e69-4c46-b0d8-1b742f6efb89
- Dominant language
- C++
- Stars
- 389
- Forks
- 88
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/mobile
-
bug iOS 🍎 ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4744 ·
Maintainers usually reply within 1 day
-
bluetooth bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MerginMaps/mobile#4741 ·
Maintainers usually reply within 1 day
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MerginMaps/mobile#4669 ·
Maintainers usually reply within 1 day
-
bug Good first issue ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4665 ·
Maintainers usually reply within 1 day
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/mobile#4647 · 1 comment ·
Maintainers usually reply within 1 day
All issues in MerginMaps/mobile
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CleverRaven/Cataclysm-DDA#88974 ·
Maintainers usually reply within 1 day
-
comp-mysql
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ClickHouse/ClickHouse#124749 ·
Maintainers usually reply within 1 day
-
Status: Needs confirmation Status: Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day