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

Citrix Remote Desktop: [*] key behaving oddly #1440

Open
Rainforce15 opened this issue Nov 25, 2021 · 3 comments
Open

Citrix Remote Desktop: [*] key behaving oddly #1440

Rainforce15 opened this issue Nov 25, 2021 · 3 comments

Comments

@Rainforce15
Copy link

Describe your issue

Plover works in most applications including most remote desktop software like the regular Windows RDP client.
When connected to a Citrix Remote Desktop (Windows server, Windows client), letter/symbol keystrokes are sent correctly, however using [*] behaves in one of three odd ways inside the remote environment:

  1. deletion works as expected (only a few cases; in Notepad, Outlook)
  2. no characters get deleted (in e.g. Some Text Editors, Firefox, Chrome, search bar and browser text-input fields)
  3. The textual backspace character 'BS' (Code 0x08) is printed into the text input field, exactly as many as expected deletions (Notepad++)

The third point is possibly the same as the second, just that the applications given in 2) do not render the BS character.
I assume this is a Citrix issue, but wonder if there is a workaround.

Steps you've taken

  • Tried changing Keyboard Layouts on both client and server
  • Tried changing the Keyboard layout/IME sync settings in the Citrix Client (unsure if it worked, or is overwritten by server policies)

Expected behavior

Deletion works correctly.

Screenshots

image

Operating system

  • OS: Windows 10
  • Plover: plover-4.0.0.dev10+120.g4394ef1

Hardware

Tested with

  • a Splitography with Plover in TxBolt mode
  • a regular keyboard with Plover in Keyboard mode
@user202729
Copy link
Member

Might be same issue as one of the issues linked from #1436 (comment) .

I don't have the software to test right now.

@Rainforce15
Copy link
Author

Will check workaround/fix in #1410 (comment) later and report back.

@Rainforce15
Copy link
Author

Rainforce15 commented Nov 25, 2021

Compiling the code with said changes makes it work! Thank you @user202729

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants