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

Cursor jumping to top left of stacked windows when using shortcut to switch #792

Closed
ProspectPyxis opened this issue Dec 25, 2020 · 6 comments · Fixed by #800
Closed

Cursor jumping to top left of stacked windows when using shortcut to switch #792

ProspectPyxis opened this issue Dec 25, 2020 · 6 comments · Fixed by #800

Comments

@ProspectPyxis
Copy link

ProspectPyxis commented Dec 25, 2020

(1) Issue/Bug Description:

When switching between stacked windows using keyboard shortcuts (Super+H and Super+L in particular, though any other custom shortcuts do the same thing), the cursor seems to jump to very near the top left of the window affected. As far as I know, this has not happened until recently on my end.

Here's an image of how it looks like:
Peek 2020-12-25 18-47

(2) Steps to reproduce (if you know):

  1. Stack at least two windows together.
  2. Use keyboard shortcuts to cycle between them.

Unfortunately, I have no idea how the bug activates - it seems to have started out of nowhere, and has been a consistent issue since it started.

(3) Expected behavior:

The cursor should stay where it originally was.

(4) Distribution (run cat /etc/os-release):

Pop!_OS 20.10

(5) Gnome Shell version:

3.38.2

(6) Pop Shell version (run apt policy pop-shell or provide the latest commit if building locally):

pop-shell:
  Installed: 1.1.0~1608318806~20.10~19ebae0
  Candidate: 1.1.0~1608318806~20.10~19ebae0
  Version table:
 *** 1.1.0~1608318806~20.10~19ebae0 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu groovy/main amd64 Packages
       1001 http://ppa.launchpad.net/system76/pop/ubuntu groovy/main i386 Packages
        100 /var/lib/dpkg/status

(7) Where was Pop Shell installed from:

Came installed with Pop!_OS.

(8) Monitor Setup (2 x 1080p, 4K, Primary(Horizontal), Secondary(Vertical), etc):

Single 1080p monitor.

(9) Other Installed/Enabled Extensions:

  • Auto Move Windows
  • Caffeine
  • Clipboard Indicator
  • Frippery Move Clock
  • Panel OSD
  • System Monitor
  • Workspace Buttons

(10) Other Notes:

None.

@mphojele
Copy link
Contributor

This is a feature under an Xorg session. On Wayland you won't have this.

@ProspectPyxis
Copy link
Author

Hm...I'm aware that this might fall out of the scope of pop shell specifically, but is there any way to disable this within xorg? Reading through the issues page, it seems this with wayland still has some issues to resolve, so I'd like to avoid that if possible.

@mphojele
Copy link
Contributor

I use a wayland session. Anyways, I can't seem to find an obvious way disable this feature. Code related to it is in

/** Move pointer when you switch applications */
and
/// Activates a window, and moves the mouse point.

A hack would be to comment out line 560 in src/window.ts, but when you run make local-install it might complain because the function would be defined but never called, which means comment out the function definition as well.

@ProspectPyxis
Copy link
Author

Wow, if this was implemented two months ago according to the blame, I really wonder how I haven't noticed it as a problem until now. Either way, I find it really weird that there's no way to disable this easily right now, despite the configuration option for it being right there (but unused as far as I can tell)...how hard would it be to add it as an easy configurable option, in that case?

@mmstick
Copy link
Member

mmstick commented Dec 29, 2020

This has been a feature since before Pop Shell supported tiling, because it improves mouse utility on ultrawide displays. But I can disable this for switching between stacks, since it's not necessary to do so for stacked windows.

@ProspectPyxis
Copy link
Author

Ahh, that makes more sense. That does sound like a good solution.

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

Successfully merging a pull request may close this issue.

3 participants