Hi,

It took me a while to understand why I had to use mouseemu in conjunction with
pommed to make the latter work.

Pommed has a built-in list of product ids it will accept as keyboards. Whenever
a new model comes out, pommed will refuse to use it. One the other hand, it
will gladly use the Mouseemu Virtual Keyboard, which is much less fussy about
what devices it should open.

I see two (non-exclusive) solutions:
  1- accept any keyboard;
  2- provide a runtime configuration option in which the user can specify which
device to use. I suggest this option should concern directly the product id:

  general {
        # If pommed fails to detect your internal keyboard, put here the
product id listed by lsusb
        product_id = 05ac:0253
  }

If you agree on such a scheme, I can work on a patch.

Kind regards, Thibaut.

I would like to see an update on this, at least some confirmation from
the maintainers to acknowledge this suggestion. If the original reporter
(fairly) is no longer willing to do this, I would be happy to try,
despite my inexperience.