<span class="gmail_quote"><br></span>Dear Sir,<br>
<br>
The code does same thing as existing code and why this is a layer violation and existing one is not ?<br>
It just get LED status change instead of setting it and this make OSD
design clean and clear without polling LED status and make unnecessary
Xlib dependency .<br>
<br>BR,<br>Sam<br><br><br><div><span class="gmail_quote">2007/11/28, Daniel Stone <<a href="mailto:daniel.stone@nokia.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">daniel.stone@nokia.com</a>
>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span class="e" id="q_11684592d80e0d21_1">
On Wed, Nov 28, 2007 at 03:47:46AM +0800, ext Sam Lin wrote:<br>> For tablet/UMPC there is a requirement to make NumLock/CapsLock status<br>> visible on systray or on OSD and<br>> that make condition signal of such status change from
addon-input.c helpful.<br><br>Please don't do this. All your interaction with keyboards is through X,<br>so why cause a layering violation? Just ask X for the LED status.<br><br>Cheers,<br>Daniel<br><br></span></div>
-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.6 (GNU/Linux)<br><br>iD8DBQFHTKMk68xJuWtYYdURAsuoAJ9rnRId7RaHFJ8Z+zZMSdB1fLUjwgCfaZVF<br>iZKisTX86aHBzQCqUcnv8hc=<br>=U/Oi<br>-----END PGP SIGNATURE-----<br><br></blockquote></div><br>