Package: pommed
Version: 1.39~dfsg-3.1
Severity: wishlist
Tags: upstream
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.
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.9-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pommed depends on:
ii eject 2.1.5+deb1+cvs20081104-13
ii libasound2 1.0.25-4
ii libaudiofile1 0.3.4-2
ii libc6 2.13-38
ii libconfuse0 2.7-4
ii libdbus-1-3 1.6.8-1+deb7u1
ii libpci3 1:3.1.9-6
Versions of packages pommed recommends:
ii dbus 1.6.8-1+deb7u1
pommed suggests no packages.
-- Configuration Files:
/etc/pommed.conf changed [not included]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
