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 cannot move between outputs when using non-contiguous positioning #8519

Open
Crystal4276 opened this issue Jan 3, 2025 · 3 comments
Labels
enhancement New feature or incremental improvement

Comments

@Crystal4276
Copy link

Crystal4276 commented Jan 3, 2025

Sway Version:

1.10

Debug Log:

Configuration File:

# Minimal configuration to reproduce
output DP-1 pos 0 0 mode [email protected] scale 1.5
output DP-2 pos 2630 0 mode [email protected]
output DP-3 pos 6140 0 mode [email protected] scale 1.5

Stack Trace:

Not applicable - no crash

Description:

Steps to reproduce:

  1. Configure multiple outputs with intentional gaps between them using non-contiguous pos values as shown in config above
  2. Move cursor to the right edge of DP-1 screen
  3. Observe that cursor stops at the edge instead of transferring to DP-2
  4. Move cursor to right edge of DP-2 screen
  5. Observe that cursor stops at the edge instead of transferring to DP-3

Expected behavior: Cursor should transfer between outputs when reaching screen edges, even with non-contiguous positioning.

Current behavior: Cursor stops at screen edges and does not transfer between outputs when there are gaps in the positioning values.

This makes it difficult to use multi-monitor setups where users want visual separation between outputs while maintaining easy cursor navigation. Common use cases include accommodating wide monitor bezels or intentionally creating visual workspace separation.

@Crystal4276 Crystal4276 added the bug Not working as intended label Jan 3, 2025
@emersion emersion added enhancement New feature or incremental improvement and removed bug Not working as intended labels Jan 3, 2025
@emersion
Copy link
Member

emersion commented Jan 3, 2025

This is the intended behavior, so flagging this as an enhancement instead.

Related: #6607

@Crystal4276
Copy link
Author

Thanks for the feedback.

Looking at issue #6607, the proposed solution there looks slightly different to what i would like to use.
I'm specifically looking for the cursor to be able to traverse through intentional gaps between monitors - essentially "disappearing" into the gap space before emerging on the adjacent output.
It seems #6607 is recommending the cursor to warp directly to the next output.

@emersion
Copy link
Member

emersion commented Jan 3, 2025

I don't think allowing the cursor to move off-screen is a good idea. It would be too easy to "loose" the cursor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or incremental improvement
Development

No branches or pull requests

2 participants