-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When trying to screenshot Taskmanager using Printscreen button, it takes a fullscreen screenshot and doesnt use flameshot selector #3644
Comments
It seems by pressing printscreen you are running SnippingTool (Windows' default screenshot tool) and not Flameshot. Apparently Windows every now and then overwrites your settings and you should change it again. Follow these steps: |
I disabled this feature but it only stopped taking fullscreen screenshots... Ive found a small workaround without needing to do anything to the registry/add a shortcut:
|
Are you implying that the Windows TaskManager is behaving differently compared to the rest of the system? |
I guess you could say that. Its as if the TM has some kind of VIP rights that overrules the settings (unless you click out of it), because even though I have the setting to take screenshots with the print screen button disabled, it will still take a fullscreen screenshot when in TM. |
I don't have a Windows machine to test this, but I asked a friend to confirm this for me. Apparently you are absolutely right and Windows TaskManager behaves different!! I will re-open this issue although I highly doubt that this can be solved by Flameshot as it seems to be a Windows thing. |
sounds good! If this isnt a fixable thing don't worry about it, I can always just use my method to work around it 👍 |
sorry for posting on this thread again, but I just found another program that has this same behavior (the game Genshin Impact to be precise). Pressing the print screen button doesn't open flameshot but takes a fullscreen screenshot instead. I tried it in 2 other fullscreen games but it seems to work fine there. |
Thanks for keeping us updated and trying different approaches to identify the root cause of the issue.
If it is a Windows "security" thing, then it would be out of our hands.
That is already discussed in #1341 . Also the #2118 might help in some cases as well.
Perhaps they hard-coded something in their game. |
perhaps it's related to always on top? |
In the case of task manager, yes, but I don't think it's exclusively "always on top" since I have the same issue in Genshin impact (which I play in regular fullscreen). On the contrary, it works normally in trackmania2020 which I also run in regular fullscreen... |
FWIW, I am unable to take screenshots of certain applications. Task manager included, but also a lot of control panel or similar. It doesn't work with Windows Snipping, Gyazo or Flameshot. I've been unable to find out what is different with these windows that make it block print screen attempts. If the application lets you select what you want to screenshot, it ignores any mouse movement over those windows. If you try starting the selection on the app, it won't work. Soon as you move the mouse outside of the window, you have the option. It's unlikely to be the case that the Windows snipping tool, Gyazo and Flameshot all have the same 'issue' within them and it's therefore likely consistent issue throughout Windows on these; but I am yet to find out why.. |
Flameshot Version
Flameshot v12.1.0 (96c2c82)
Compiled with Qt 5.15.2
winnt: 10.0.19045
windows: 10
Installation Type
Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)
Operating System type and version
Windows 10
Description
When you try to take a screenshot of the windows taskmanager (doesnt matter if its "always on top" or not) using the Printscreen button, it will take a fullscreen screenshot instead of opening flameshot's selector to specify what to screenshot.
Steps to reproduce
Screenshots or screen recordings
No response
System Information
Windows 10 22H2
1920x1080 Laptop screen
The text was updated successfully, but these errors were encountered: