Re: input.h changes

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

Quoting Johann Deneux <jo...@Do...>:
> On Fri, 1 Feb 2002, Vojtech Pavlik wrote:
> > On Thu, Jan 31, 2002 at 10:44:28PM +0100, Johann Deneux wrote:
> > > On Thu, 31 Jan 2002, Vojtech Pavlik wrote:
> > > 
> > > For FF_ABS, maybe, but FF_BTN is still needed. It is used to trigger
> > > effects when a button is pushed.
> > 
> > Is there ever any difference between EV_KEY defined buttons and those in
> > FF_BTN? Just checking ...
> > 
> No, you are right, a button is a button, no need to have both regular
> buttons and force-feedback buttons.

Well, again I'm at work and haven't got the spec here, but I think it
says that not all buttons are neccessarily available as FF-trigger
buttons. On my joystick they all are, and while that's not exactly a
statistically significant sample, I can't really see any reason not to
have all of them FF-capable.

Ah, The deadman grip, if reported as a button, shouldn't be FF-capable.
(It kills all effects if you drop the stick.)

BTW, if anyone has a MS FF racing wheel, I'd be a happy man if they
would send me the report descriptor for it.

/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