Skip to content
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

[Feature Request] Do not hardcode "gnome-screenshot" for screenshots #360

Open
j1elo opened this issue Mar 7, 2022 · 0 comments
Open

[Feature Request] Do not hardcode "gnome-screenshot" for screenshots #360

j1elo opened this issue Mar 7, 2022 · 0 comments

Comments

@j1elo
Copy link

j1elo commented Mar 7, 2022

 * csd version: 5.2.0+una
 * Distribution: Linux Mint 20.3 Una
 * Graphics hardware *and* driver used: Intel integrated
 * 64 bit

Feature Request

Do not force usage of gnome-screenshot for the screenshot media keys. Instead, have a setting which contains the program to be used for each of the screenshot actions.

Not all actions will be applicable to all screenshot programs. For example, window capture is something that gnome-screenshot can do, but Flameshot cannot. In those cases, given that it's the user the one who wants to change this setting, it seems reasonable that choosing a more limited software falls on their responsibility.

In any case, it doesn't look too user friendly to force usage of gnome-screenshot like now (see it hardcoded in source here). Thus this feature request to allow modification.

Steps to reproduce

  • Open "System Settings" on Cinnamon.

  • Under "Hardware", open "Keyboard".

  • Under "Shortcuts", find "Take a screenshot".

  • Become frustrated as changing the screenshot program seems like a reasonable thing to allow, but there is no hint about how to do that in the GUI. Until one finds out that what seemed counterintuitive turns out to be the expected thing right now: that the only method to change hardcoded values from csd is to disable all existing shortcuts and manually recreate them, one by one.

    It is counter-intuitive for several reasons:

    • User doesn't really want to change the actual keys needed to trigger the shortcut. So looking in that part of the settings is already confusing.
    • Still, if one reaches this GUI, it is also confusing that a default action, with a perfectly fine Name and Description, should be removed/disabled in order to manually create an identical one but with a different command.

Expected behaviour

  • ... (same initial steps)
  • Under "Shortcuts", find "Take a screenshot".
  • For each entry, have a GUI field that allows to set a different callback command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant