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

macOS: keyboard does not work when macOS lockscreen is displayed #59

Open
warpdesign opened this issue Apr 5, 2024 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@warpdesign
Copy link

Describe the Bug/Issue

I am using Cursr with a mac and a PC with Windows. When the mac's lockscreen appears, I can still use the mac's mouse on the Windows computer, but the mac's keyboard doesn't work anymore: typing something appears on the mac's lockscreen instead of the Windows where the mouse is.

Steps to Reproduce

  1. Connect a Mac and a Windows PC
  2. Make sure the Mac's keyboard can be used to control the Windows PC
  3. Make the Mac's lockscreen appear (cmd+l)
  4. Move the Mac's mouse so that it can control the PC's mouse
  5. Attempt to type some text

Expected Behavior

The text appears on Windows.

Your Environment

  • OS details: Windows 10 x64/MacOS ARM 14.3.1
  • Cursr Version: 1.6.6
  • License: Free
@ragauskl ragauskl added the enhancement New feature or request label Apr 5, 2024
@ragauskl
Copy link
Contributor

ragauskl commented Apr 5, 2024

Functionality when lockscreen is active is not officially supported yet, but it is in the to-do list. Mouse currently works but it was not intended/implemented, it's simply because macOS still allows mouse events to pass, that also means keyboard events also happen but macOS does not allow Cursr to capture/listen on them when lockscreen is active.

Cursr will likely require elevated permissions to do so, but I haven't looked into this implementation yet and cannot guarantee it. You can try to run it with elevated permissions and see if that solves the issue. But when not necessary I don't recommend running Cursr in elevated permissions as that makes it harder to shut it down in case of an issue, with proper implementation I may be able to require elevated permissions only when necessary making it safer to use in case of an issue

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

No branches or pull requests

2 participants