<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 Bill Spitzak, thanks for your opinion. : )<o:p></o:p><o:p> </o:p>As we know, there are a lot of keyboards or keyboard-like devices.<o:p></o:p>Some of them will be keypads or special keyboards for game or other purposes.<o:p></o:p>For those kinds of keyboards, we don’t need to care and we can deal with the events in the usual manner (e.g. send them to focus surface/window).<o:p></o:p><o:p> </o:p>When it comes to mobile or TV, we can have another stories.<o:p></o:p>In mobile/TV, in some cases, we need to deal with a set of keys attached in the device in a special manner, therefore we need to distinguish the keys in the set from the normal keyboard keys.<o:p></o:p><o:p> </o:p>For instance, in mobile, we can see some keys attached in our mobile devices.<o:p></o:p>Those kinds of keys are usually not for input texts but for triggering some actions.<o:p></o:p>In a usual application, volume up/down keys will be the keys for raising/lowering the volume.<o:p></o:p>By the way, in an application like a message application, volume up/down keys can be used to adjust the font size.<o:p></o:p>Therefore each key attached in mobile device needs to be sent to each needed surface/window in a dynamically changeable delivery policy for each key because there are many applications which want to get a key even they don’t have the input focus.<o:p></o:p>Actually in many requirements in mobile devices, distinguishing between the normal(?) keyboards and the special set of key/buttons are needed and we need to have a key delivery manager which resides in a window manager for sending the special set of keys to the proper application(s).<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: Bill Spitzak [mailto:spitzak@gmail.com] Sent: Friday, September 25, 2015 4:37 AM To: 박성진 Cc: Andreas Pokorny; Peter Hutterer; wayland Subject: Re: [PATCH] libinput device capability modification regarding combo input devices<o:p></o:p><o:p> </o:p><div><o:p> </o:p><div><o:p> </o:p><div>On Wed, Sep 23, 2015 at 6:52 PM, 박성진 <<a href="mailto:sj76.park@samsung.com" target="_blank">sj76.park@samsung.com</a>> wrote:<o:p></o:p><div><div>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></div></div><div><o:p> </o:p></div><div>Seems like the keyboard flag can just indicate a "full keyboard". It is hard to imagine an input device that does not have a few buttons so this can be assumed.<o:p></o:p></div></div></div></div></div></body></html>