home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sgi.hardware:49 comp.sys.sgi.graphics:84
- Newsgroups: comp.sys.sgi.hardware,comp.sys.sgi.graphics
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!news.belwue.de!sun1.ruf.uni-freiburg.de!kleinren
- From: kleinren@sun1.ruf.uni-freiburg.de (Rainer Kleinrensing)
- Subject: Spaceball and 4.0.5
- Message-ID: <1993Jan2.150024.6325@sun1.ruf.uni-freiburg.de>
- Organization: Rechenzentrum der Universitaet Freiburg, Deutschland
- Date: Sat, 2 Jan 93 15:00:24 GMT
- Lines: 32
-
- Hello there,
- we have a 4D-220VGX equipped with a spaceball. Under 3.x there was a program
- called spaceballd that handled that device. You also could use the
- spaceball as a mouse (i.e. move the mouse cursor using the spaceball) and
- do such things as calibrating it and so on.
-
- After having installed 4.0 (currently 4.0.5) emulating the mouse doesn't
- work anymore. However, that is merely annoying. My question is why I find the
- following messages in SYSLOG:
- Dec 28 12:00:43 gt unix: WARNING: data event with unknown format.
- Dec 28 12:00:43 gt unix:
- Dec 28 12:00:43 gt unix:
- Dec 28 12:00:43 gt unix: WARNING: unexpected byte 0xA3 in packed mode
- Dec 28 12:00:43 gt unix:
- Dec 28 12:00:43 gt unix:
- Dec 28 12:00:43 gt unix: WARNING: Bad length for data event (0 words)
- Dec 28 12:00:43 gt unix:
-
- They seem to occur every time I use the spaceball (from a locally written
- application that uses the spaceball since 3.X days). Has the format of
- spaceball events changed ?
- I also noticed that there is a rather long delay (1-2 sec) between moving
- the spaceball and seeing the result on screen. That was not the case
- under 3.X
- Thanks for any hints,
-
- --
-
- Rainer Kleinrensing, rainer@indigo.mathematik.uni-freiburg.de
- Institute for Applied Mathematics
- Freiburg University
-