Received: from cs.utah.edu by karazm.math.UH.EDU with SMTP id AA09914 (5.65c/IDA-1.4.4 for ); Tue, 8 Oct 1991 22:54:40 -0500 Received: from peruvian.utah.edu by cs.utah.edu (5.65/utah-2.18-cs) id AA03547; Tue, 8 Oct 91 21:50:52 -0600 Received: by peruvian.utah.edu (5.65/utah-2.12s-leaf) id AA04800; Tue, 8 Oct 91 21:50:49 -0600 Date: Tue, 8 Oct 91 21:50:49 -0600 From: galt%peruvian@cs.utah.edu (Greg Alt) Message-Id: <9110090350.AA04800@peruvian.utah.edu> To: glove-list@karazm.math.uh.edu Subject: PC hires source I uploaded source code for a PC... I converted the ST code and fixed it up a little. I was thinking, we should probably have a standard interface of some sort so that our code will be relatively compatible. Here is my proposal: typedef struct _glove_data { unsigned char dum0; signed char x,y,z; unsigned char rot,fingers,keys,dum7,dum8,dum9,dumA,dumB; } glove_data; void Hires(); void getglove(glove_data *); possibly better function names would be glove_init() and glove_sample() Also, the byte that I called "dum9" seems to be used to tell if the glove is not aimed at the receivers. One more thing I was wondering about... In the initialization function, it looks like 7 bytes are sent to the glove. I wonder what the significance of these is... The reading of the first few bits is probably to tell if a glove is really attached. The other thing to start brainstorming about is how to solve the problem of the 5 long pauses. Each one is 14 milliseconds, so you waste 70 milliseconds per sample. Surely something useful could be squeezed into that time somehow. Also, that only gives us 14 samples per second (assuming nothing else is done between samples). Tonight I plan on experimenting with the finger input (I played around with x,y,z, moving a simulated 3D cursor around, and it was kind of interesting) Greg