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
It does associate prt scr button with snippingtool, but that is not the issue.
ShareX and Greenshot (abandonware from 2017) disassociates snippingtool from the prt scr key on behalf of the user. The developers do not direct Windows users "Hey, you have to figure this out and do all this stuff to make it work for you as a Windows user."
What I am seeing in this project is this "If you install Flameshot on Windows then you as the user need to jump through these hoops because us Flameshot developers are not going to do it for you on Windows."
So tell me "Flameshot is a Linux tool\utility and not really meant for Windows without saying Flameshot is a Linux tool\utility and not really meant for Windows."
I think Flameshot is superior to other screenshot software, but its usability is fatally flawed on Windows until the project developers drop the Plugin way of doing things (which has been discussed for years but no action taken), and figure out how to deliver simple usability for Windows users such as how to trigger Flameshot screenshot via key combo and timestamps.
Other projects can do it. So it is not as if it is not possible. What I am talking about is a Flameshot project developer issue. I go back to one thing - the project developers are focused on Linux and Windows is an afterthought.
Flameshot Version
Flameshot v12.1.0 (96c2c82)
Compiled with Qt 5.15.2
winnt: 10.0.26100
windows: 10
Installation Type
Using the ready-made package from Github Releases
Operating System type and version
Windows 11 24H2
Description
prt scr does not work for Flameshot on Windows 11 24H2
Steps to reproduce
Screenshots or screen recordings
No response
System Information
Edition Windows 11 Pro
Version 24H2
Installed on 9/6/2024
OS build 26100.2314
Experience Windows Feature Experience Pack 1000.26100.32.0
The text was updated successfully, but these errors were encountered: