GNOME Bugzilla – Bug 719919
Default screenshot keybinding behavior
Last modified: 2019-03-20 11:15:08 UTC
I think gnome-shell screenshot functionality should display a notification that indicates where the screenshot image is saved. As an extra, the default image viewer would be opened with the screenshot on click on the notification.
(In reply to comment #0) > I think gnome-shell screenshot functionality should display a notification that > indicates where the screenshot image is saved. No, we definitively don't want that. For instance when opening the "Background" settings panel, gnome-control-center will take a screenshot for the top bar preview - in that case, gnome-shell's screenshot functionality is merely an implementation detail and should not be exposed to the user in any way. So if we want notifications in some cases, opening them should be left to the caller rather than implementing it in the backend. Reassigning to gnome-settings-daemon, assuming that the main issue are the PrintScrn shortcuts.
> Reassigning to gnome-settings-daemon Oh, right. I've filed this bug report against gnome-shell, but I was not sure it was the right Product.
*** Bug 738949 has been marked as a duplicate of this bug. ***
[ changed the summary to not imply a particular solution ] Currently we have the following keybindings (configurable on Settings > Keyboard > Shortcuts > Screenshots): Save to Pictures [ Print ] Copy to Clipboard [ Ctrl+Print ] I believe Windows does copy to clipboard by default on Print alone. Perhaps it would be enough if we changed our default action to copy to the clipboard *in addition* to saving to Pictures ?
(In reply to Rui Matos from comment #4) > I believe Windows does copy to clipboard by default on Print alone. Perhaps > it would be enough if we changed our default action to copy to the clipboard > *in addition* to saving to Pictures ? I think storing the picture by default is okay as long as there is a discoverable route to the file. The current behaviour has a really disrupting workflow: - People who don't know where the picture is stored by default might be a bit confused as to where to find it once they've pressed "Print" (regardless of clipboard or disk) - If stored at the disk, and several screenshots have been mide, a quick peek at ~/Pictures would mean that once has to carefully look at the date/time part of the file name since thumbnails of that size are usually quite similar. A notification pointing to the right file would make the screenshot->(open/share/modify) workflow a lot smoother.
This issue has been discussed at length in the past. Previously, there have been two principal arguments against showing a notification for every screenshot: 1. If you take a few screenshots in sequence it becomes very jarring, and the notification itself could be in the way of taking the next screenshot. 2. Typically, the next step after taking a screenshot is to upload it somewhere. Opening the screenshot through a notification doesn't help with this. If we are going to discuss this, we need to be clear about what the goals are. Is it a discoverability issue - that people don't know where the screenshot has been stored - or to do with making the workflow easier? If discoverability is the issue, then showing a notification every time is a bit overkill, since the same location is used every time. However, showing a notification the first time someone takes a screenshot (and only the first time) could make sense: "Screenshots can be found in the Photos application or the Pictures folder." Alternatively, if making the workflow for taking and sharing screenshots is the concern, we can consider: * Copying the screenshot to the clipboard, in addition to saving it as a file. * Adding sharing functionality to Photos (to upload to common websites, for example). * Revamping the Screenshot app, to allow you to annotate, enable image upload and so on.
My main concern at the moment is the discoverability (if we find a solution, it would be worth considering something similar equivalent for screecasts). I do share your concerns about one notification-per screenshot being a problem. But of course I do feel the current workflow is a bit akward, but this is personal taste so take it with a pinch of salt, indeed this is probably a more complicated issue to solve. Usually I want to do screenshot+crop+share either by email or something like that, but of course there is the less common but still relevant screenshot+gimp/editing workflow. I am not sure if my specific usecase is common enough or at all.
> 1. If you take a few screenshots in sequence it becomes very jarring, Right. The "Suppressed file" in-app notification in Files has this issue. and > the notification itself could be in the way of taking the next screenshot. That could be mitigated by automatically hiding it before the next screenshot. > 2. Typically, the next step after taking a screenshot is to upload it > somewhere. Opening the screenshot through a notification doesn't help with > this. It's possible to open an application by clicking on a notification, isn't it ? > If discoverability is the issue, then showing a notification every time is a > bit overkill, since the same location is used every time. However, showing a > notification the first time someone takes a screenshot (and only the first > time) could make sense: This is my main concern. I guess a single notification could be enough, but may be it could be a single notification by day, or by session. It's easy to forget an information given a while ago. > "Screenshots can be found in the Photos application or the Pictures folder." It's not really related to this bug, but I do think photos should only show photos, not screenshots, clipart, or random images found in the picture folder.
I put a patch in bug 753894 which is somewhat related to this discussion.
(In reply to Emmanuel Pacaud from comment #8) ... > > the notification itself could be in the way of taking the next screenshot. > > That could be mitigated by automatically hiding it before the next > screenshot. I honestly don't know if this is possible or not. If it is, it would be additional complexity, of course. > > 2. Typically, the next step after taking a screenshot is to upload it > > somewhere. Opening the screenshot through a notification doesn't help with > > this. > > It's possible to open an application by clicking on a notification, isn't it > ? The notification could include a button to open with an application or two, yes. But how is that useful. In most cases, people want to upload the screenshot to the web. > > If discoverability is the issue, then showing a notification every time is a > > bit overkill, since the same location is used every time. However, showing a > > notification the first time someone takes a screenshot (and only the first > > time) could make sense: > > This is my main concern. I guess a single notification could be enough, but > may be it could be a single notification by day, or by session. It's easy to > forget an information given a while ago. You could possibly do something like "notify if more than 1 month since the last screenshot", or something. Although, again: that's more complexity.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/239.