WeThotUWasAToad
asked on
Restore Windows 7 Snipping Tool function to Windows 10
Hello,
After recently upgrading from Windows 7 to Windows 10, I noticed that the Snipping Tool (ST) now requires an extra click. I use ST frequently and therefore have it pinned to my taskbar in both Windows versions. With Windows 7, one click on the ST taskbar icon put you immediately into the hazed-screen and ready-to-snip mode. However, with Windows 10, clicking the taskbar icon only brings up the ST toolbar (which is fairly small and commonly difficult to locate right off). An additional click on the toolbar is then required before snipping can occur.
Is there a way to change that behavior back to how it was in Windows 7? I looked through the Options and other menus but was not able to find it.
Alternatively, is it possible to install the Windows 7 ST on to Windows 10 or is any other workaround available?
Thanks
After recently upgrading from Windows 7 to Windows 10, I noticed that the Snipping Tool (ST) now requires an extra click. I use ST frequently and therefore have it pinned to my taskbar in both Windows versions. With Windows 7, one click on the ST taskbar icon put you immediately into the hazed-screen and ready-to-snip mode. However, with Windows 10, clicking the taskbar icon only brings up the ST toolbar (which is fairly small and commonly difficult to locate right off). An additional click on the toolbar is then required before snipping can occur.
Is there a way to change that behavior back to how it was in Windows 7? I looked through the Options and other menus but was not able to find it.
Alternatively, is it possible to install the Windows 7 ST on to Windows 10 or is any other workaround available?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Wait, wait :-)
Why MS did it: because the shortcut is now CTRL together with print screen.
Why MS did it: because the shortcut is now CTRL together with print screen.
> Why MS did it: because the shortcut is now CTRL together with print screen.
Regardless of what the shortcut or hotkey is, the default, imo, should not be to bring it up in non-snipping mode. There may be reasons to take down the dialog, which can be done with Cancel/Escape, but the far better default is to bring it up in snipping mode, as W7 does. They should not have changed the default in W8 and W10 to bring it up in non-snipping mode. Regards, Joe
Regardless of what the shortcut or hotkey is, the default, imo, should not be to bring it up in non-snipping mode. There may be reasons to take down the dialog, which can be done with Cancel/Escape, but the far better default is to bring it up in snipping mode, as W7 does. They should not have changed the default in W8 and W10 to bring it up in non-snipping mode. Regards, Joe
Totally agree. That shortcut is only good when snipping tool is already running and will do nothing when you close it. Should not have brought it up.
ASKER
[b]...there's a simple work-around with our friend, AutoHotkey.[/b]
Thanks for the script Joe. AHK was to be my fallback strategy but you beat me to it. :) I'm sort of glad though because it raises two questions, one of which I will ask here and the other in a new thread.
Question: [b]How did you know to use ^{PrintScreen} as the shortcut?[/b]
I would have used:
[code]#s::
Run,C:\Windows\Sysnative\S nippingToo l.exe
WinWaitActive,Snipping Tool
Send !n
Send r
Return[/code]
Thanks for the script Joe. AHK was to be my fallback strategy but you beat me to it. :) I'm sort of glad though because it raises two questions, one of which I will ask here and the other in a new thread.
Question: [b]How did you know to use ^{PrintScreen} as the shortcut?[/b]
I would have used:
[code]#s::
Run,C:\Windows\Sysnative\S
WinWaitActive,Snipping Tool
Send !n
Send r
Return[/code]
ASKER
That's odd, that the closing comment will not accept tags. Hmm, I wonder if it has always been that way or if it's a glitch. Here it is again (with quote tags this time):
Thanks for the script Joe. AHK was to be my fallback strategy but you beat me to it. :) I'm sort of glad though because it raises two questions, one of which I will ask here and the other in a new thread.
Question #1: How did you know to use ^{PrintScreen} as the shortcut?
I would have used:
...there's a simple work-around with our friend, AutoHotkey.
Thanks for the script Joe. AHK was to be my fallback strategy but you beat me to it. :) I'm sort of glad though because it raises two questions, one of which I will ask here and the other in a new thread.
Question #1: How did you know to use ^{PrintScreen} as the shortcut?
I would have used:
#s::
Run,C:\Windows\Sysnative\SnippingTool.exe
WinWaitActive,Snipping Tool
Send !n
Send r
Return
ASKER
Actually, my second question was to be about "Sysnative" but I quickly found an explanation via Google so no need for a new thread.
> That's odd, that the closing comment will not accept tags. Hmm, I wonder if it has always been that way or if it's a glitch.
It's been a glitch forever — was reported almost three years ago:
https://www.experts-exchange.com/bugs/2956/Bolded-question-post-is-sent-to-email-with-BBCode-instead-of-HTML-mark-up.html
The same glitch appears in the new "Help resolve this question" process — was reported more than three months ago:
https://www.experts-exchange.com/bugs/19687/Closing-comment-box-in-the-new-Help-resolve-this-question-process-ignores-the-BBCode-tags.html
> How did you know to use ^{PrintScreen} as the shortcut?
Through experimentation. Ctrl-N also works and Alt-N also works. So your AHK script will work, but there's no need for the Send r — the Send !n is sufficient.
> "Sysnative"
Glad to see you figured that out — I had to research it, too. My first attempt was %windir%\system32\Snipping Tool.exe, which fails miserably. :) Regards, Joe
It's been a glitch forever — was reported almost three years ago:
https://www.experts-exchange.com/bugs/2956/Bolded-question-post-is-sent-to-email-with-BBCode-instead-of-HTML-mark-up.html
The same glitch appears in the new "Help resolve this question" process — was reported more than three months ago:
https://www.experts-exchange.com/bugs/19687/Closing-comment-box-in-the-new-Help-resolve-this-question-process-ignores-the-BBCode-tags.html
> How did you know to use ^{PrintScreen} as the shortcut?
Through experimentation. Ctrl-N also works and Alt-N also works. So your AHK script will work, but there's no need for the Send r — the Send !n is sufficient.
> "Sysnative"
Glad to see you figured that out — I had to research it, too. My first attempt was %windir%\system32\Snipping
Is that what you get? Normal for Windows 10 and now a different tool than Windows 7