Maul Window 0.7.0

Maul Window 0.7.0 closes the gaps an audit of 0.6.0 against the requirements found: input methods on X11, the keys the platform keeps as a typed fact, monitor hotplug tested on the platform, and the touch keyboard on Win32.

Added

• Input methods on X11 (mwin-0030): IBus through its portal and Fcitx 5 over the session bus, Fcitx first when XMODIFIERS names it. Keys go to the input method without stalling the frame and are held in order until it answers (at most 100 ms); a key it takes is dropped, compositions arrive as mwin_eventImePreedit with segments and caret, committed text as mwin_eventTextInput, and the candidate window follows the caret.
• Keys the platform keeps (mwin-0031): mwinGetKeyReach tells whether a chord, a key with modifiers, is delivered, shared with the platform, uncertain (the desktop's configurable shortcuts may take it) or never delivered, from a table per platform. On the web, Chromium's own chords (Ctrl+W, Ctrl+T, Ctrl+N) never arrive. mwinTestSetKeyReach sets the test backend's answers.
• The touch keyboard on Win32 (mwin-0033): mwinRequestVirtualKeyboard shows and hides it through the window's InputPane (Windows 10 1607 and later), denied where a hardware keyboard is attached; the purpose sets the window's input scope; the part of the window it covers comes as mwin_eventVirtualKeyboardChanged.

Fixed

• X11 reports monitors set or deleted through RandR (xrandr --setmonitor, a desktop splitting a wide display), which the X server tells only as the root window's ConfigureNotify. Platform tests now plug monitors in and out on Wayland and X11.

Recorded

• Input methods on Win32 stay on IMM32, which receives every TSF input method through TSF's bridge (mwin-0032).