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

KeyDown Event Firing in Windows #1

Open
bkeeney opened this issue Sep 3, 2013 · 3 comments
Open

KeyDown Event Firing in Windows #1

bkeeney opened this issue Sep 3, 2013 · 3 comments

Comments

@bkeeney
Copy link

bkeeney commented Sep 3, 2013

The keydown event does not fire in Cocoa but still fires in Windows (unknown about Linux). That may cause some unpredictable behavior in legacy applications that have just switched to using the TextInputCanvas plugin.

@tempelmann
Copy link

Shouldn't the title of this bug be reworded to include "only", or renamed to ".. not in Cocoa"? Otherwise, it makes little sense. I gather you want it to fire in Cocoa, not stop firing in Windows?

@bkeeney
Copy link
Author

bkeeney commented Sep 4, 2013

No. The event does NOT fire in Cocoa nor do you want it to. It is a legacy event that means nothing for TextInputCanvas.

In Windows, this event still fires which is wrong. It should not fire at all to match what Cocoa does.

@donl
Copy link

donl commented Dec 4, 2015

On Cocoa, I am seeing KeyDown events when the control returns false on the IsEditable event. So far this works great for me (I need both modes).

I have yet to test on Windows/Linux.

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

3 participants