More bugs in pfuGetEvents?

New Message Reply Date view Thread view Subject view Author view

Roy Ruddle (Ruddle++at++cardiff.ac.uk)
Thu, 11 Feb 1999 09:19:55 +0000 (GMT)

> On Wed, 10 Feb 1999, Mario Veraart wrote:
>
> I have found what could be a bug in the code of pfuGetEvents.
> Depending on the time that it takes to get the forked X-input process
> initialised you have the value of the returned structure also
> uninisialised.

Mario suggested a fix for this problem (events.numDevs unitialised).

I've also hit that problem and also found that events.numKeys doesn't
alswys get initialised. I currently trap this by manually checking for
  if( events.numKeys > PFUDEV_MAX_INKEYS )

Another bug I've hit is that mouse button pressed and releases are
frequently missed by pfuGetEvents(). This happens on more than one type of
hardware so it looks like a s/w problem.

Before I get my hands dirty (+ bearing in mind I'm not an X expert), has
anyone else encountered (preferably fixed!) these problems

cheers

roy

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Thu Feb 11 1999 - 01:20:48 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.