Hi,
You're using X right? I can't find a way with Xlib to find which keyboard
generated the event. I also don't have an extra keyboard to plugin at the
moment.
Try running 'xev' in a terminal. Then press a key on each keyboard, and
see if there are any differences in the output.
They should print something like this:
"""
KeyPress event, serial 36, synthetic NO, window 0x4600001,
root 0xad, subw 0x0, time 223972330, (-345,178), root:(450,225),
state 0x4, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (03) ""
XmbLookupString gives 1 bytes: (03) ""
XFilterEvent returns: False
"""
Maybe copy them back to the email so we can all have a look.
cheers,
On Fri, Nov 4, 2011 at 9:33 PM, pierrelafran...@sympatico.ca <
pierrelafran...@sympatico.ca> wrote:
> Debian on Atom-PC like computer / Python / Pygame
> Thanks
>
>
> --
> Pierre
>
>
> On 11-11-04 03:07 PM, René Dudfield wrote:
>
>> Hi,
>>
>> It might be possible to get that information with a system message.
>> What platform/s do you need to support?
>>
>> cheers,
>>
>> On Fri, Nov 4, 2011 at 7:37 PM, pierrelafran...@sympatico.ca
>> <mailto:PierreLafrance1@**sympatico.ca <pierrelafran...@sympatico.ca>> <
>> pierrelafran...@sympatico.ca
>>
>> <mailto:PierreLafrance1@**sympatico.ca <pierrelafran...@sympatico.ca>>>
>> wrote:
>>
>> Hi
>> We have an application using a Digital Keyboard like this one :
>>
>> http://www.targus.ca/ca/__**product_details.asp?sku=__**AKP10CA<http://www.targus.ca/ca/__product_details.asp?sku=__AKP10CA>
>>
>>
>> <http://www.targus.ca/ca/**product_details.asp?sku=**AKP10CA<http://www.targus.ca/ca/product_details.asp?sku=AKP10CA>
>> >
>>
>> Now our application need many of them, and our application must
>> distinguish all key from all keyboard. For example, when user press
>> enter from keyboard 1, we must know the KP_ENTER is from keyboard 1,
>> and same thing for keyboard 2...n
>>
>> Is this possible with Pygame (according to our web search this seams
>> to not feasible with Pygame, but I'm hopping you prove me wrong and
>> we will not have to do that at SDL level... (please...)
>>
>> Thanks,
>>
>> --
>> Pierre,
>>
>>
>>
>
