https://bugs.kde.org/show_bug.cgi?id=443060

John B <john+kde_...@daaave.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |john+kde_...@daaave.org

--- Comment #12 from John B <john+kde_...@daaave.org> ---
I'd like to request this feature as well; there are workarounds (of varying
effectiveness), but it seems like something that could really benefit from just
officially being supported.

For example, the comment before this suggests an interesting workaround that
_almost_ does the trick, but not quite.  I want to capture a particular window
with multiple sequential screenshots, but when I use this workaround the
following happens:

1. I set the capture mode to "Active Window", activate the window, and hit
PrtScr.  Spectacle successfully captures the window.
2. I press Return (after manually navigating the active button around to the
"Save" button, which is a bit non-intuitive but perhaps not a deal-breaker) and
Spectacle successfully saves the screenshot.  So far, so good.
3. PLOT TWIST: When I saved the screenshot, Spectacle itself became the active
window; when I hit PrtScr again, I get a picture of the Spectacle window.

My best thought for a UI to enable this while creating the smallest amount of
new UI possible (I know we're in Apple mode here 'cause the window doesn't even
have a proper Close/Quit button :P) is to add a checkbox below the current ones
(below "Quit after manual Save or Copy" in my version) that says something like
"Immediately save to default location on capture".

Although, I suppose at that point you've still got to deal with having
Spectacle become the active window when you click in it or press PrtScr.

As an aside, I've created a feature request to capture a specific window by its
properties; I definitely feel like this is a different issue that should also
be addressed, but adding that functionality should solve for my particular use
case.  Here's the link, in case anybody else is interested:
https://bugs.kde.org/show_bug.cgi?id=449986

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to