Re: input.h changes

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

Quoting Johann Deneux <jo...@Do...>:
> On Thu, 31 Jan 2002, Bj|rn Augustsson wrote:
> > Quoting Johann Deneux <jo...@Do...>:
> > > Note the arrays. There is one value for each axis. The axis mumber has
> > > become useless and has therefore been droped.
> > 
> > I wondered about this part when reading the spec. Why two axes? Why not
> > 3? Or "n"?  This seems a bit joystick-centered, I can easily imagine a
> 
> Indeed. Then we would need a list of (parameter/axis id) pairs.
> That sounds doable.

Yes. On the other hand, it's difficult to tell if it's ever going to be
needed... Hmm. I'd like to cheat again, and have a look at what MS
DirectInput does.

> > How would you feel about renaming shape to envelope? It fits the PID
> > spec, and it has some precedent from audio waveforms.
> 
> Ok. I can also change the ff_interactive_effect to ff_condition_effect,
> if you prefer.

OK, that'd be good too.

> > Antother thing we might want to add to the API is supporting the "Start
> > Solo" action on an effect, in addition to the "start" and "stop" that we
> 
> What do you mean ? One can only start one effect at a time ? Or do you
> mean to play an effect to play once ? That's already supported.

According to the PID spec (5.9), it means "Start the effect specified by
the Effect Handle and stop all other effects." As opposed to "Start" which
means "Start the effect specified by the Effect Handle". 

/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