I am using the client (v 1.3.6) on a 1.5ghz powerbook g4 under
mac os x 10.3.4.
I found that the keyword mapping on Mac OS X can become
corrupted after using the client to connect to our application. The
symptoms are that keys don't transmit properly, with transmitted
values not being the correct key or some non-printing key. Even
after quitting the client, this behavior persists. Multiple reboots and
even a powerdown may be required to recover the correct
keyboard behavior.
As yet, we do not know exactly what key strokes or mouse events
lead to the corruption.
These problems did not previous occur, when running a 500mhz
powerbook G4 under mac os x 10.3.3.
Logged In: YES
user_id=351330
I can't think of anything Chicken would do to cause this to occur _after_
the app has been quit. Can you verify that it is indeed Chicken causing
the issue and not general problems with your system?