[UX/Feature Request]: Screenshot Editor Improvements (Fixed Zoom Bar & Persistent Tool Settings)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
No files or tests are named. Start by locating the Screenshot Annotation/Editor tool and inspect how the zoom controls, selected drawing tool, sidebar properties, and settings state are handled. Done means non-obstructive fixed zoom controls, persistent tool selection and live properties, with separate tool settings retained across sessions.
Written by the indexing model from the issue text.
Description
Hi @richiemcilroy,
While using the Screenshot Annotation/Editor tool, I noticed two major user experience (UX) friction points that slow down the editing workflow significantly.
I would love to see the following improvements to make the annotation process much more fluid:
1. Pin the Zoom Controls (Avoid Floating Overlaps)
Currently, the Zoom (+ / -) controls float directly on top of the canvas.
- The Problem: When zooming into an image or when resizing the Editor window to a smaller scale, these floating buttons frequently overlap the actual screenshot content, making edits near that area difficult or impossible.
- Proposed Solution: Instead of a floating bubble, please integrate the zoom controls into a fixed, stationary bottom toolbar layout so they never obstruct the canvas content.
2. Tool Behavior, Live Previews & Session Persistence
Right now, drawing shapes (like arrows or rectangles) feels clunky due to three limitations:
- Immediate Tool Reset: The moment I finish drawing an arrow, Cap instantly switches back to the default "Select" tool. If I want to draw 3 arrows in a row, I have to re-click the arrow icon 3 times.
- No Pre-Draw Customization: I cannot adjust properties like Stroke Width, Color, or Opacity before drawing. I am forced to draw a default shape first and modify it retroactively.
- No Persistence: Cap does not remember the style settings of the tools.
Proposed Solution:
- Keep Tool Active: Keep the selected drawing tool active until the user manually presses
Escapeor switches to another tool. - Live Properties: Allow users to adjust Stroke Width, Color, and Opacity in the sidebar before placing the element.
- Tool-Specific Persistence (Across Sessions): Save the last used settings individually for each tool (e.g., Arrows stay Red with 100% Opacity, while Rectangles can have a distinct Blue style). These preferences should persist across app restarts and new sessions.
This would elevate Cap's built-in annotation tool to the level of professional standalone screenshot utilities!
Greetings, Denny
- Dominant language
- Rust
- Stars
- 25k
- Forks
- 2.4k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 676
Getting set up
- Ships a 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 CapSoftware/Cap
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Download, FAQ, privacy and terms pages have no meta descriptionPossibly taken @patrickballard claimed this 13 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CapSoftware/Cap#3675 · 1 comment ·
Maintainers usually reply within 1 day
-
self hosting
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#2384 · 3 comments ·
Maintainers usually reply within 1 day
-
Dashboard pagination causes full page reloads on self-hosted CapPossibly taken @DipanshuAmbilkar03 claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CapSoftware/Cap#2305 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#1714 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day