| Summary: | Overwrite already-saved screenshot when explicitly saving after annotating while using the "After taking screenshot, save file to default folder" setting | ||
|---|---|---|---|
| Product: | [Applications] Spectacle | Reporter: | gudvinr+kde |
| Component: | General | Assignee: | Boudhayan Gupta <me> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | ciprian.m.vizitiu, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 22.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
gudvinr+kde
2022-09-10 13:32:04 UTC
Are you using the "After taking screenshot, save file to default folder" setting, by any chance? (In reply to Nate Graham from comment #1) > Are you using the "After taking screenshot, save file to default folder" > setting, by any chance? Yes, I do. I meant that by "options <...> save on disk enabled". That's kinda main point of this issue. I don't annotate screenshots most of the time so it'd be annoying to save them manually every time just to add annotations (and it won't solve issue with creating secondary annotated screenshot anyway). But when I do annotate it suddenly creates rather bad experience because I need to explicitly save image because after you press "annotation done" annotation is not, in fact, done and it creates litter in screenshot folder. Well, you kind of did it to yourself. :) You told Spectacle to auto-save after taking a screenshot, which it did. If you then annotate the screenshot, it's up to you to replace the already-saved screenshot. Maybe we can special-case this, though. Well, I'd say there is one real issue here: 1. Screenshot is saved as expected 2. When you call annotation, ANOTHER copy of same image is being created This behaviour can't be explained by any of the settings spectacle has. And even if it did, it couldn't be a thing that anyone wants because saving 2 copies of the same message into same folder just doesn't make any sense from practical standpoint. I agree that thing with 3rd image is not an issue per se and rather a bit of an annoyance. Yes, I'd rather have it overwritten. It could be an option, even. "Overwrite image after annotation" or something like that. But it is not a bug. Wanted to file a bug about screenshot naming behavior for annotated images and got redirected here. I always use "Save As" for annotated images and I've noticed that the "Save As" dialog will suggest as filename the very string defined in "Configure Spectacle -> Image Saving -> Filename:" e.g. `Screenshot_<yyyy><MM><dd>_<HH><mm><ss>` instead of say 'Screenshot_20250121_113120' IF the image has been modified by Spectacle's own editor. The behavior is odd if not a plain bug because the very same "Save As" dialog, when invoked from the same Spectacle window but WITHOUT any annotation done, will suggest the filename with the placeholders correctly replaced by actual values. Is it the same problem or I should open a separate issue for this? |