If I start to pre-edit something, and then switch to passthrough mode with F12, the pre-edit state is not reset. I'm guessing the right thing to do is send a preedit event with a NULL/empty string followed by done?

Hey, I'm trying to build this on FreeBSD but I get an error where meson complains that libanthyinput can't be found. I'm able to build wlhangul just fine, so I'm trying to find out if it is an issue with the ja-anthy package in FreeBSD.

Running meson build/ gives me:

The Meson build system
Version: 0.59.1
Source dir: /usr/home/kallinen/code/wlanthy
Build dir: /usr/home/kallinen/code/wlanthy/build
Build type: native build
Project name: wlanthy
Project version: 0.0.0
C compiler for the host machine: cc (clang 11.0.1 "FreeBSD clang version 11.0.1 ([email protected]:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)")
C linker for the host machine: cc ld.lld 11.0.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Compiler for C supports arguments -Wno-missing-braces: YES 
Compiler for C supports arguments -Wno-unused-parameter: YES 
Found pkg-config: /usr/local/bin/pkg-config (1.7.4)
Run-time dependency anthy found: YES 0.4

meson.build:29:1: ERROR: C shared or static library 'anthyinput' not found

meson-log.txt

Forwarding keys with virtual-keyboard has a performance penalty (input latency). The key travels in this way:
compositor -> im -> compositor -> end_client

We need to forward keys based on our state sometimes (e.g. Return, Tab, Backspace). We could tell the compositor at connection time the set of keys we would like to receive for each of the "states" and tell the compositor every time the state changes. In this way forwarding has no penalty:
compositor -> end_client

But we would need to extend the input-method protocol for this. Is it doable?

For wlanthy the partial keyboard grab config would look like this:
In state 0, we want to receive: Space...asciitilde
In state 1, we want to receive: Space...asciitilde+F5...F8+Return+BackSpace+Tab+Left_Tab+Alt_L (mod)
Important: If any modifier is active, the compositor must not send keys unless we specified that modifier in the list. If the user presses Ctrl+A, we don't want to catch A. But if we are in state 1, we do want to receive Alt+Tab.

The partial grab is configured by issuing multiple times (for different values of state) this request:

<request name="configure_grab">
  <arg name="state" type="uint"/>
  <arg name="ranges" type="array"/>
  <arg name="singles" type="array"/>
</request>

And in order to notify the compositor of a state change:

<request name="state_change">
  <arg name="state" type="uint"/>
</request>

But... for this to work, the above must be sent every each key event (even if the state stays the same), and the compositor must wait for it before sending the next.

Another approach might be to statically configure also the keys that change states so the compositor is automatically aware:

<request name="configure_transitions">
  <arg name="state_i" type="uint"/>
  <arg name="state_f" type="uint"/>
  <arg name="singles" type="array"/>
</request>

So:

<interface name="zwp_input_method_keyboard_grab_v2" version="2">
...
  <request name="configure_grab">
    <arg name="state" type="uint"/>
    <arg name="ranges" type="array"/>
    <arg name="singles" type="array"/>
  </request>

  <request name="configure_transitions">
    <arg name="state_i" type="uint"/>
    <arg name="state_f" type="uint"/>
    <arg name="singles" type="array"/>
  </request>
...
</interface>

Hi,

I found a weird (and somewhat problematic, at least for me) behavior: on the first launch of wlanthy, it uses the keymap of the first keyboard I type on (fr-oss for the built-in keyboard and bepo for the external keyboard) but if I kill it (^C), I have to wait ~10-15 minutes or the keymap used by wlanthy will be qwerty (no other software seems to be impacted).

While I don’t really mind being restricted to the first keymap used on launch*, I would prefer being able to simply restart wlanthy when I un-/dock the laptop (and changing which physical keyboard I use) without waiting 10-15 minutes before being able to use it again.

Any idea on how to diagnose/fix this? 🙂

In case it helps:

• Sway v1.6.1
• VoidLinux
• Linux 5.12.17_1
• wlanthy from master (6cf315a) launched manually via foot 1.8.2

とにかく,wlanthyを生み出してありがとう! (apologies for any mistake, I have much to learn still 😛)

* Obviously, it would be best if the underlying keymap could change on the fly but it would be more of a nice-to-have feature ^^

The check must be done after UTF-8 conversion.

Some keys, like the arrow keys, are passed through to the client while pre-editing. As a result, I can "move" whatever I'm pre-editing in e.g. vim.

Not sure if the above description is clear enough. Let me know if it's not.

Hi, I use sway and up until recently I only used two keyboard layouts(none of which are Japanese), and switched between them in the following way in the .config/sway/config file:

input * {
    xkb_layout "us,il"
    xkb_options "grp:caps_toggle"
}

I would like to make it possible so that when I press tab, the keyboard layout would still change like it does now, but also "toggle" to the wlanthy service so that I could seamlessly switch between all three languages using tab. How can I do this?