You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the grab screen area feature has been previously used, it should remember and default to that selection on subsequent uses.
Problem
I want to take screenshots that will comprise a series (e.g., of a process that I’m documenting). I want all my screenshots to have the same dimensions and for elements within them to not jump around.
Currently, I have no way ensuring that any two selections I make are of the same coordinates and size.
Proposal
The grab screen area mode should remember its previous location and dimensions and default to it.
The text was updated successfully, but these errors were encountered:
Hm, since it's currently always a rubberband, this would require completely changing the current workflow. Which might be desired anyway, but it's not as simple as it sounds in this issue. 😉
For prior art, I know GNOME designers have recently spent time thinking through how screenshots should work on GNOME; it might be worth checking out their work and seeing what (if anything) we want to borrow. One of the core concepts there is that it actually grabs the screen immediately, and then allows cropping (instead of separate rubberbanding at the time of taking the screenshot). That makes a lot of sense to me and it more how it works on Android as well.
If the grab screen area feature has been previously used, it should remember and default to that selection on subsequent uses.
Problem
I want to take screenshots that will comprise a series (e.g., of a process that I’m documenting). I want all my screenshots to have the same dimensions and for elements within them to not jump around.
Currently, I have no way ensuring that any two selections I make are of the same coordinates and size.
Proposal
The grab screen area mode should remember its previous location and dimensions and default to it.
The text was updated successfully, but these errors were encountered: