BUG: 386481
Details
Diff Detail
- Repository
- R166 Spectacle
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage
The referenced bug number misses a 1, should be 386481 -> https://bugs.kde.org/show_bug.cgi?id=386481
What is the motivation for this change?
Seems including the cursor or not when invoking the shortcut might be something different people would have different expectations for. E.g. I would not expect the cursor to be captured.
This seems a random change to me, ideally such things should be based on design and use cases analysis, not single users poking by a bug report (which misses all those users happy with the current behaviour).
My 2 cents as user who just recently fixed a bug in Spectacle, but is not a maintainer (thus also resigning from this review).
This only changes the default behavior when you invoke spectacle using a global keyboard shortcut. One argument in favor of changing this is that it brings consistency, since the cursor is captured by default when you use the main UI.
Perhaps what we should do is add a new dbus invocation that doesn't specify whether or not to capture the cursor and makes the decision itself by reading Spectacle's pre-existing user preferences.
Abandoning this since there's no consensus on whether or not this is the right approach.