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

Type Text doesn’t work with MS Remote Desktop #1792

Open
skurfer opened this issue Mar 7, 2014 · 5 comments
Open

Type Text doesn’t work with MS Remote Desktop #1792

skurfer opened this issue Mar 7, 2014 · 5 comments

Comments

@skurfer
Copy link
Member

skurfer commented Mar 7, 2014

The below has been fixed by #1827. The only outstanding issue is outlined in the last comment here


It inserts an ‘s’ for every character typed.

Probably something in #1536

An edge case maybe, but Remote Desktop is actually one of the most useful places for this action, since clipboard communication isn’t always reliable.

@skurfer skurfer added this to the 1.2.0 milestone Mar 7, 2014
@skurfer skurfer added the Bug label Mar 7, 2014
@pjrobertson
Copy link
Member

So #1536 introduced this bug?
If it's a v1.2.0 show stopper then we need to figure out a fix. Any ideas?
Any way I can test without remote desktop?

@skurfer
Copy link
Member Author

skurfer commented Mar 18, 2014

I haven’t had time to look into it much. If I find another app that’s affected, I’ll let you know. Any ideas what I can check on my end?

@skurfer
Copy link
Member Author

skurfer commented Apr 18, 2014

For what it’s worth, I can reproduce this using CoRD, too. It doesn’t seem to happen in other MS applications or in Carbon applications.

@pjrobertson
Copy link
Member

I have reopened this, since #1827 didn't fully fix this.

It seems that for certain apps that can't deal with unicode strings properly, certain characters get mangled. See @skurfer's one remaining problem

@skurfer skurfer removed this from the 1.2.0 milestone May 1, 2014
@stale
Copy link

stale bot commented Apr 4, 2022

This issue hasn't been updated in over 2 years. It has been marked as 'stale' and will be closed in 30 days. Please check whether this is still an issue with the latest version of Quicksilver. If so, update or comment on this issue to keep it open.

@stale stale bot added the noactivity label Apr 4, 2022
@skurfer skurfer removed the Bug label Apr 5, 2022
@stale stale bot removed the noactivity label Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants