Clarification on dead keys

[k0nserv]

I did some reasearch based on #263 using a simple macOS app that just logs keyDown events. With my layout(based on Swedish Pro) ^, ¨, ~ don't work correctly since they are dead keys. Handling dead keys involves quite a bit more work that needs to be done in winit. I'm curious if handling dead keys is considered in scope for winit or if that's something that you expect applications themselves to deal with.

Also see alacritty/alacritty#682

[elinorbgr]

For comparison, the wayland platforms automatically handles dead keys. By that I mean that for example:

• User presses ^ key (which is a dead key on my azerty keyboard)
• winit generates a KeyPressed event for key ^ but no ReceivedCharacter event
• User then presses e key
• winit generates a KeyPressed event for key e, then a ReceivedCharacted('ê')

So we have a discrepancy between backends, time to decide what to converge to.

[tomaka]

What @vberger described is what should happen IMO. That's also currently the behaviour on Windows.

Might want to have a look at https://stackoverflow.com/questions/40088837/cocoa-objective-c-on-macos-handle-accented-characters-via-keydown?rq=1