They're on the list, if they get a chance to reply they will.  I'm not sure
if it's a Pygame error or SDL or what.  Do you know what device your
keyboard is mounting to?  Try using lsusb on your dev platform and again on
your ARM platform, and see if they're mounting to different locations.  Then
you might be able to force it to mount to the same location on the ARM
platform as it does on your dev platform, and then perhaps the event parsing
will be correct.  You should not be getting identical events for different
keypresses though.

On Wed, Aug 19, 2009 at 7:46 PM, pierrelafran...@sympatico.ca <
pierrelafran...@sympatico.ca> wrote:

> Luke Paireepinart wrote:
> > Sorry, no idea.  You could perhaps dig into the event processing part of
> > Pygame but the hardware interface may be on the C/SDL side rather than
> > Python.  I'm sure Rene or Lenard or someone more knowledgeable can help.
> >
> > On Wed, Aug 19, 2009 at 4:34 PM, pierrelafran...@sympatico.ca
> > <mailto:pierrelafran...@sympatico.ca> <pierrelafran...@sympatico.ca
> > <mailto:pierrelafran...@sympatico.ca>> wrote:
> >
> >     Luke Paireepinart wrote:
> >     > If it's working in a text editor then Linux has the drivers working
> on
> >     > your embedded platform.  I would first try just printing out every
> >     event:
> >     >
> >     > while 1:
> >     >     for event in pygame.event.get():
> >     >         print event
> >     >
> >     > If pygame is not getting the event then you probably will need to
> look
> >     > into mapping the device (from /dev/kb1 or whatever) so Pygame reads
> it
> >     > for event input.
> >     >
> >     > On Wed, Aug 19, 2009 at 3:36 PM, pierrelafran...@sympatico.ca
> >     <mailto:pierrelafran...@sympatico.ca>
> >     > <mailto:pierrelafran...@sympatico.ca
> >     <mailto:pierrelafran...@sympatico.ca>> <pierrelafran...@sympatico.ca
> >     <mailto:pierrelafran...@sympatico.ca>
> >     > <mailto:pierrelafran...@sympatico.ca
> >     <mailto:pierrelafran...@sympatico.ca>>> wrote:
> >     >
> >     >     Hi
> >     >     I have a question on keyboard, about an issue we have.
> >     >
> >     >     We develop a pygame application on a desktop, using Ubuntu
> >     7.10.  But
> >     >     target is an embedded ARM board, runing a custom made linux
> >     distro, base
> >     >     on Debian (kernel 2.4).  So far, we managed to make
> >     application works on
> >     >     both platforms.
> >     >
> >     >     But now we're trying final setup, using a Logitech wireless
> >     numeric
> >     >     keyboard (pruduct number : 920-000217).
> >     >
> >
> http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3075&cl=ca,en
> >     <
> http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3075&cl=ca,en
> >
> >     >
> >     <
> http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3075&cl=ca,en
> >     <
> http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3075&cl=ca,en
> >>
> >     >
> >     >     The Pygame application works this wireless keyboard on Ubuntu
> >     7.10.
> >     >     The Pygame application doesn't work with this wireless keyboard
> on
> >     >     embedded ARM platform.
> >     >
> >     >     But, keyboard works fine on embedded ARM platform, in a text
> >     editor, or
> >     >     at command line.  So the custom Linux distro detect the USB
> >     dongle and
> >     >     keyboard works fine.  But only Pygame application on embedded
> ARM
> >     >     doesn't work with  this keyboard.
> >     >
> >     >     Do you have any suggestion to help me debug this problem ?
> >     >     Thanks
> >     >
> >     >
> >     >     Pierre
> >     >
> >     >
> >
> >     Hi
> >     This is event received on Pygame apps, runing on our embedded ARM
> >     plateform, when pressing key 1 to 9 on the wireless keyboard :
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >     <Event(2-KeyDown {'key': 300, 'unicode': u'', 'mod': 0})>
> >     <Event(3-KeyUp {'key': 300, 'mod': 0})>
> >
> >     Any idea on whats happening ?
> >     Thanks
> >
> >     Pierre
> >
> >
>
> Hi
> Thanks for your support.
> How can I get in touch with these guys ?
> Thanks
>
> Pierre
>

Reply via email to