Wismill
Wismill
I asked [feedback](https://bugreports.qt.io/browse/QTBUG-118698) to Qt devs.
Not too happy with the `XKB_COMPOSE_CANDIDATE_ACCEPTED` state. But if we return just `XKB_COMPOSE_COMPOSED`, then the client should handle the last keysym as not part of the sequence.
I sent a [merge request](https://codereview.qt-project.org/c/qt/qtbase/+/516630) in Qt.
Idea: use headless Weston
[xwayland-run](https://gitlab.freedesktop.org/ofourdan/xwayland-run) would be most useful, but there is an issue with all the headless compositors: there is no input by default nor an easy way to add some! It seems...
Cheap solution: - If using RMLVO API, then the value is known before parsing: just use it. - Otherwise: - Set `last = 3 * XKB_MAX_GROUPS`. We expect only realistic...
The are two issues with includes here: - bad syntax: it should fail early. We may be lenient for some other syntax issues, but I think we should not for...
I extracted the commit “[Actions that would not break a latch no longer prevent it](https://github.com/xkbcommon/libxkbcommon/pull/569/commits/d7b4797404a0c3d471a31d80847b603532ec917e)” into #611. Good catch!
As for the rest of the MR, I will pause new features development until [1.10](https://github.com/xkbcommon/libxkbcommon/milestone/5). But things that break the XKB specification will require more time to asset. I am...
Current status: Any new lock breaks all existing latches New latches break existing latches for non-preserved modifiers in the modifier list of the type of the key that triggered the...