<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style></style></head><body lang=KO link=blue vlink=purple><div class=WordSection1>Dear Andreas Pokorny, thanks for your reply. J<o:p></o:p><o:p> </o:p>As you mentioned, we also need to distinguish between a full keyboard and a device which has a set of few keys.<o:p></o:p>Each key coming from the full keyboard will be sent to the focus surface(window).<o:p></o:p>However, a key coming from the device which has a few keys sometimes needs to be sent to the other surface(window) other than the focused surface(window).<o:p></o:p><o:p> </o:p>Dear Peter Hutterer, any ideas on this patch ? J<o:p></o:p><o:p> </o:p>Thanks and regards,<o:p></o:p>Sung-Jin Park<o:p></o:p><o:p> </o:p>From: Andreas Pokorny [mailto:andreas.pokorny@gmail.com] Sent: Wednesday, September 23, 2015 3:48 PM To: 박성진 Cc: wayland-devel@lists.freedesktop.org Subject: Re: [PATCH] libinput device capability modification regarding combo input devices<o:p></o:p><o:p> </o:p><div><div>Hi,<o:p></o:p><div>2015-09-23 4:29 GMT+02:00 박성진 <<a href="mailto:sj76.park@samsung.com" target="_blank">sj76.park@samsung.com</a>>:<o:p></o:p><div><div>Dear all,<o:p></o:p>as you guys know, there are some combo input devices which support both keyboard functionality and pointer functionality.<o:p></o:p>We can also see some of input devices supports both keyboard functionality and touch functionality.<o:p></o:p> <o:p></o:p>In theory, each input device functionality needs to be provided through each kernel device node.<o:p></o:p>By the way, there are many combo input devices whose input events is coming from one device node.<o:p></o:p>Now and in near future, many vendors can make many combo input devices.<o:p></o:p> <o:p></o:p>For these kinds of input devices, how about adding new enums for combo devices?<o:p></o:p>Otherewise, how about defining enums with masks ?<o:p></o:p></div></div><div> For that reason we do use masks inside mir to describe input devices. We do use a few additional masks to also indicate whether the device, i.e. it might be interesting to know whether the device is a full keyboard or just offers a few buttons.. So yes I aggree with that. Right now we do the evdev based device detection in parallel to what udevd and libinput do.. <o:p></o:p></div><div>regards<o:p></o:p></div><div>Andreas Pokorny<o:p></o:p></div></div><o:p> </o:p></div></div></div></body></html>