Hyun Kang.
- Original Message -
Sender : Peter Hutterer
Date : 2020-05-22 12:32 (GMT+9)
Title : Re: Question about Linux MT Protocol B type
On Thu, May 21, 2020 at 07:42:33PM +0900, 강정현 wrote:
> Dear all,
>
> I have an one question about Linux MT Protocol B type.
>
>
Dear all,
I have an one question about Linux MT Protocol B type.
Asume that press touch screen using first finger.
And release fisrt finger and press second finger toghether.
In that case, which procotol is correct?
ABS_MT_SLOT 0
ABS_MT_TRACKING_ID 1
Dear all.
I have known that locale data (for libxkbcommon) is exist in /usr/share/X11/locale/ normally.
And that is provided in libX11.
(refer libxkbcommon's documentation)
Dataset
libxkbcommon does not distribute a keymap dataset itself, other than for testing purposes. The
Hello, guys.
I have a one question about the libinput API.
I want to share your opinions about duplicated device added events via udev.
Suppose to duplicated device add events(about a same device) are occurred.
Currently libinput opens two fd about a same event node.
So that I have a question
Hello, guys.
I have a one question about the libinput API.
I want to get device's bustype to know how this device is connected.
But there is no thie API and that API is supported only in libevdev.
But other APIs to get device information are supported(abstracted) in
libinput.
Dear, Mr. Pekka Paalanen.
Thanks you for your rapid reply and
I understand what you mean.
Yes, I just want to make like weston-info.
But I want to insert extra information than weston-info.
Weston-info just print interface's name/version/id about user defined
interface.
So I can't print
Dear, Mr. Pekka Paalanen.
Thank you for your reply and opinion.
I have checked Mr. Giulio's patch:
https://patchwork.freedesktop.org/series/4181/
But unfortunately my patch was little different with Mr. Giulio's.
His patch is to watch interfaces binded such clients.
So He added
Hello, guys.
When I check mouse wheel events using libinput,
I found that this wheel value was always converted by libinput.
Like this: wheel_degrees.y = -1 * e->value * device-
>scroll.wheel_click_angle.
In function evdev_process_relative().
That value is set using udev property named
Hello, guys.
I have a query regarding linux MT protocol event handling in libinput side.
I wanted to get the extra events such as ABS_MT_TOUCH_MAJOR,
ABS_MT_PRESSURE as an event of libinput,
but I found that libinput doesn't handle those events.
Thus I'd like to know whether there is any plan
Dear Peter and guys,
thank you for your information about Andreas Pokorny's patches.
As I checked them out, most of them seem to make sense to me. :)
I have more queries. Would you please kindly answer to me?
1.
How can we send the touch pressure/area events via wayland protocol?
I know this
10 matches
Mail list logo