Bug 363628 - Usability bug: spectacle should by default ask for a filename on saving
Summary: Usability bug: spectacle should by default ask for a filename on saving
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-28 14:49 UTC by Halla Rempt
Modified: 2017-02-20 18:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 16.04


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Halla Rempt 2016-05-28 14:49:08 UTC
Gnome's screenshot utility is already bad saving screenshots by default as "Screenshot from 2016-04-16 11-03-03.png", but Spectacle is worse by using  a nearly unparsable sequence of numbers: "Screenshot_20160528_164215.png". Neither is useful at all: the default on saving should be to open a file dialog. The file dialog should, of course, remember the last folder where the user saved the screenshot to.
Comment 1 Boudhayan Gupta 2016-05-28 16:01:43 UTC
Version?

In 16.04 onwards, the save button doesn't always show Save & Exit, it shows the last-used save action. If you once use the Save As function (instead of Save & Exit), the button will be Save As from the next time onwards, until the time you next use another save option.

As for the default filename, it's configurable. If you can suggest a better default pattern, do tell me - I'm open to suggestions and changes :-)
Comment 2 arne anka 2016-09-13 10:58:25 UTC
as for "Save & Exit" vs last used: that's not true for Debian/Sid (Version: 16.04.3-1). I always use "Save As ...", but the action selected when starting is still always "Save & Exit"

additionally: having "Preferences" as entry in the "Save"-actions dropdown seems rather misplaced.
Comment 3 Peter Wu 2016-10-11 23:43:26 UTC
Boudewijn, do you need additional changes? What is the behavior you expect?
If you had issues with the save location not being persisted (bug 357817), that is fixed since 16.04.

Arne, I cannot reproduce your issue with 16.08.1, does it still occur after restarting Spectacle?
Comment 4 Halla Rempt 2016-10-13 08:51:02 UTC
Hi Peter,

I'll update my system -- it's current still 15.something, where selecting a different save action doesn't do anything at all. What I would expect is that if I use save-as once, it'll be selected next time I run spectacle. If that's fixed, then the issue can be closed, of course.