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

KeyRelease event not triggered for CMD+X on MacOS #381

Closed
TGlas opened this Issue Apr 29, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@TGlas

TGlas commented Apr 29, 2013

In MacOS, when pressing a key in combination with the CMD modifier, say CMD+S for "save", then SFML does not generate a KeyReleased event for the additional key, here the 'S'.

This is possibly related to issue #377.
The same code can be used to reproduce the bug.

Observed behavior when pressing CMD+S and releasing the keys afterwards:

[KeyPressed]  key code: 40
[KeyPressed]  key code: 18
[TextEntered]  unicode: 115 character: s
[KeyReleased]  key code: 40

Expected behavior:

[KeyPressed]  key code: 40
[KeyPressed]  key code: 18
[TextEntered]  unicode: 115 character: s
[KeyReleased]  key code: 18
[KeyReleased]  key code: 40

The other modifiers (shift, control, alt) work as expected.

A side issue: is sending the text event 's' intended is this case? I would prefer not to see this event. However, it is more important to have the policy consistent across operating systems. I.e., is there a text event sent for windows key + s?

@ghost ghost assigned mantognini Apr 30, 2013

@mantognini

This comment has been minimized.

Show comment
Hide comment
@mantognini

mantognini Apr 30, 2013

Member

Good catch. There's indeed a bug with the release of keys.. but probably not related to #377.

A side issue: is sending the text event 's' intended is this case?

That would be #7 I guess.

Member

mantognini commented Apr 30, 2013

Good catch. There's indeed a bug with the release of keys.. but probably not related to #377.

A side issue: is sending the text event 's' intended is this case?

That would be #7 I guess.

@mantognini

This comment has been minimized.

Show comment
Hide comment
@mantognini

mantognini Jun 27, 2013

Member

A side issue: is sending the text event 's' intended is this case?

After thinking a little bit more about this issue I also think we should not get those events.

Member

mantognini commented Jun 27, 2013

A side issue: is sending the text event 's' intended is this case?

After thinking a little bit more about this issue I also think we should not get those events.

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