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

atomic-kms: hardware cursor disappears crossing screen boundaries #3677

Open
Saviq opened this issue Nov 19, 2024 · 0 comments · May be fixed by #3742
Open

atomic-kms: hardware cursor disappears crossing screen boundaries #3677

Saviq opened this issue Nov 19, 2024 · 0 comments · May be fixed by #3742
Labels
bug triaged Triage into JIRA to plan it in
Milestone

Comments

@Saviq
Copy link
Collaborator

Saviq commented Nov 19, 2024

Steps:

  • run Mir with --display-config=sidebyside --platform-display-libs=mir:atomic-kms --cursor=hardware
  • move the mouse across the screen boundary

Current:

  • cursor disappears

Expected

  • cursor workable

Workaround:

  • --cursor=software
@Saviq Saviq added the bug label Nov 19, 2024
@Saviq Saviq modified the milestones: 2.18, 2.19 Nov 19, 2024
@RAOF RAOF added the triaged Triage into JIRA to plan it in label Nov 29, 2024
RAOF added a commit that referenced this issue Feb 7, 2025
`KMSOutput::has_cursor` was misleadingly named, and so we implemented it
incorrectly. It is *used* to tell whether or not a cursor image needs
to be set on that particular output before it is visible, *not* whether
that output *supports* a cursor.

Rename it to something hopefully more easily understandable, and
then fix the implementation.

Fixes: #3677
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triaged Triage into JIRA to plan it in
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants