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

⌨ Better Keyboard Experience ⌨ #41

Open
FailureSam opened this issue May 8, 2023 · 2 comments
Open

⌨ Better Keyboard Experience ⌨ #41

FailureSam opened this issue May 8, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@FailureSam
Copy link

Keyboard Problem

When moving the wireless mouse between host, I find that the MacBook Magic Keyboard then becomes unresponsive, almost like it resets in way that it forgets where it is...

Steps to Reproduce

  1. A wireless mouse connected on the Windows host
  2. A M1 MacBook Pro (Likely any MacBook/ OS)
  3. Magic Keyboard connected to MacBook (likely any keyboard).
  4. Move the windows mouse to the MacBook
  5. MacBook Attached Keyboard fails to operate properly.

Expected Behavior

Any keyboard connected regardless of what host it is on should always seamlessly operate on any of the connected host. There shouldn't be a frustration after transitioning host and typin just to find out it is not.

My Environment

  • OS details: Windows 11 Pro x64, MacOS Ventura 13.2.1 (I know... I need to update -_-)
  • Cursr Version: v1.5.0-beta.4
  • License: Pro

Other

Great job on the v1.5.0-beta.4 update- Fixed the Scroll annoyance and overall smoothness!

@ragauskl
Copy link
Contributor

ragauskl commented May 9, 2023

@computesam Currently this is a known limitation of Cursr (If I remembered correctly I mentioned it in the release notes of the app) the 'input focus' follows the mouse, so if you start typing on Windows device and then move mouse to Mac, even tho you moved just the mouse, it will only be able to type in the Mac.

This is related to the fact that to 'hide' the mouse on Windows i need to create a focused window that captures the mouse but prevents sending other events to other windows. I initially attempted to do the solution you're asking for but there were too many obstacles (especially on one of the OSs) to deal with for the time being so I went with the faster solution for the Beta releases. But rest assured that fix for this is already of high priority and will be done in one of the upcoming few releases

@ragauskl ragauskl added the enhancement New feature or request label May 9, 2023
@FailureSam
Copy link
Author

@ragauskl great explanation! Thanks for the update :)

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