v0.8.9-alpha

The RDP half of #9. The reporter came back after 0.8.6: it was fixed for SSH, and the same keys still came out wrong over RDP. He was right, and it was the same mistake sitting in a second place.

Fixed: Option could not type its characters into an RDP session

The path that sends ordinary typing to the remote read the character the key would produce with Option not applied. So a layout that types @, [, ], { or } through Option sent the bare letter instead — q where Turkish Q means @.

It now reads what the layout actually produced. The comment above that line already described the intended behaviour correctly; only the property being read was wrong.

Two things came with it:

• An empty result means the layout swallowed the press as a dead key and will hand over the composed character on the next one. There is nothing to send, rather than nothing to unwrap.
• Option is a modifier to macOS but a composition key to the layout. Alt has already been pressed on the server by the time the character arrives, so sending @ while it is held reaches Windows as Alt+@ and is read as an accelerator rather than text. Alt is released for the duration of the character.

Shortcuts are untouched: Ctrl and Cmd still leave through the scancode path, which never consulted the character in the first place.

This affects every layout that reaches for Option to type programming characters — Turkish, German, Polish, Spanish, Romanian.