I tipically add a new KDE shortcut for launching Spectacle with a delay, given that it allows me to capture menus or other popup-style stuff on screen that would close on opening Spectacle otherwise.
I always wonder if this could become an option among the official Spectacle shortcuts
Yeah that makes sense, but does not adapt to my workflow. I typically just launch it and then proceed with a region capture, then have a separate shortcut to launch it with a delay.
If you use shortcuts anyway, wouldn’t it be more comfortable to directly use any of the standard shortcuts once you have opened all the relevant menus or other popup-style stuff, instead of clicking around to open the Spectacle GUI?
I do not click around but always use shortcuts. What you propose is correct, yet sadly I’ve found that on certain environments it doesnt work.
For example, if a Unity3D Editor menu is open, the shortcut simply doesnt work.
A different example is Plastic (a version control client from Unity), that closes the dropdowns as I hit PrtScr.
So my daily work environment contains apps which dont interact well with the most simple workflow.
I understand. Your idea is certainly meaningful because there are so many cases where this just doesn’t work that using a delay would be a good universal solution.
Maybe you can also investigate on why some apps behave like this and report it, just to make some noise?
Yeah maybe would be a good idea, though is it gets overly time consuming sometimes to pinpoint why Unity does what it does
In the end, I know I can bypass these and other similar/potential cases with the delay (in fact the manually added shortcut is working fine), I was just thinking that an official “Delayed Launch” shortcut for Spectacle may not be a bad idea.
so what i’m hearing is that you use the short cut with a timer to take a region snap AFTER you have set up the shot?
i did not know that was possible… if that works why have a delay at all?
the only way it’s ever worked in my experience is to start the delay and THEN set up the shot by opening the menus or what have you, and sometimes that takes longer that others so i need to set the timer before i start… sometimes 3 sec is not enough time if the menus are fiddly or nested.
No, I call the delayed start before stting up the shot. Not sure what part of what I wrote gave you the opposite impression, but I do the as you describe.
when you were describing your workflow, i think i got confused between YOUR shortcut (with the timer) and the built in shortcuts.
when i use the built in shortcuts, it ignores the timer… so that’s why i’ve taken to just calling up the UI with the timer setting and the button choices.
perhaps the change that is really needed here is for the built in shortcuts to respect the timer setting saved in the UI, or the save on click setting as well.
there might need to be an OSD of some kind to indicate that the timer is counting or that is is waiting for a click so folks using the shortcuts will know why it has not taken the snapshot yet.
so your proposal would launch spectacle and then just follow it’s configuration settings after a 3s delay, no matter what they are?
for instance, if you had it configured to use last used capture mode and the last thing you did was a full screen capture, then it would wait 3s then take full screen cap.
but what if you wanted to do a rectangular region this time?
wouldn’t you want a separate delayed version of spectacle --region --delay 3000 and spectacle --active --delay 3000, and so on? it could become unwieldy.
whereas with the respect the timer option you could simply choose the method by choosing which shortcut to use and the cap would still be saved without any GUI interaction at all.
I click None and got input, then my keyboard stopped working, means I press keys and they didn’t show up on screen so I delete all items labelled ‘action to the left side of screen shot