Re: hello...and MS-FF2...

[Bj|rn A. <d3a...@dt...>]

Quoting Rodrigo Damazio <cu...@uo...>:
>         Okay, today I looked deeper into the specs, and I found out it's 
> *partially* compliant...almost everything works according to the PID 
> specs, with a few exceptions..02(set envelope) has 7 bytes after it 
> instead of 6...06(Set ramp) has 3 bytes after it instead of 4...is this 
> the I-Force protocol?? I'm attaching some commented dumps to this message...

No, this is OK data. The joystick uses the "Device managed" sceme for
memory management. Read sections 5.11 and 9 of the PID spec and 
you'll see.

Set envelope:
	Effect block index	8
	Attack level		8
	Fade level		8
	Attack time		16
	Fade time		16
Set Ramp:
	Effect block index	8 
	start ramp		8
	end ramp		8

>         I'm sending a bzip2-ed copy here...if you want more dumps please 
> let me know(I didn't save most of my tests, I just looked at them on the 
> screen and guessed the meaning of bytes by changing parameters in 
> Immersion Studio...

Thanks a lot for this data! As I said,it's really refreshing seeing 
this stuff "from the other side". 

/August.
-- 
Wrong on most accounts.  const Foo *foo; and Foo const *foo; mean the same: foo
being a pointer to const Foo.  const Foo const *foo; would mean the same but is
illegal (double const).  You are confusing this with Foo * const foo; and const
Foo * const foo; respectively. -David Kastrup, comp.os.linux.development.system