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

Preserve cursor position when using selection mode #244

Open
JShorthouse opened this issue Dec 9, 2021 · 6 comments
Open

Preserve cursor position when using selection mode #244

JShorthouse opened this issue Dec 9, 2021 · 6 comments

Comments

@JShorthouse
Copy link

Right now the cursor gets superimposed onto the screenshot at the position it was when finishing the selection.

Which means every screenshot ends up with the cursor in the bottom right like this:

screenshot

I think what would be better is:

  1. When maim is started in selection mode, immediately save the cursor position
  2. Let the user make a selection
  3. Overlay the cursor using the initial position
@foxpy
Copy link
Collaborator

foxpy commented Dec 9, 2021

       -u, --hidecursor
              By default maim super-imposes the cursor onto the image, you can disable that behavior with this flag.

Copy-pasted straight from maim man page. If you didn't notice this flag, please close this issue, if you did and you actually mean something I don't understand, please take my apologies and try to elaborate a bit more.

@JShorthouse
Copy link
Author

Ok I will try to explain better, with a diagram.

diagram

Lets say I am trying to make a screenshot showing my mouse over a specific button. I move my mouse to where the red cursor is, and press a hotkey to open maim.

This is the position where I would like my cursor to end up in the final screenshot. I would like maim to save the cursor coordinates as soon as it is launched.

Currently the cursor always ends up where the blue cursor is (the final position after making the selection), which I don't think is very useful.

@foxpy
Copy link
Collaborator

foxpy commented Dec 10, 2021

Oh, yeah, I see what you mean. Your issue is probably not a duplicate of, but definitely closely related to #193

@JShorthouse
Copy link
Author

Yes I agree. This issue is much narrower in scope and (I imagine) would be much simpler to implement than #193. However feature-wise it's basically a subset of #193 so if #193 was implemented then this issue could be closed.

@foxpy
Copy link
Collaborator

foxpy commented Dec 10, 2021

I have some ideas how to implement #193 but I don't currently have any free time for that. Maybe during winter holidays… 🤔

@foxpy
Copy link
Collaborator

foxpy commented Jan 25, 2022

I have some ideas how to implement #193

Little update: during digging through scrot source code I have realized scrot works well when using selection and freeze options, so I no longer have any reasons to use maim so I will not work on this feature.

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

2 participants