From: Rodrigo D. <cu...@uo...> - 2002-01-26 14:03:41
|
Johann Deneux wrote: > On Sat, 26 Jan 2002, Rodrigo Damazio wrote: > >> I just realized - the interactive effect struct doesn't allow us=20 >> to assign independent parameters to the X and Y axes...it should=20 >> though, since the PID spec says there are two condition blocks for it=20 >> - one for each axis...is it okay to modify it to include separate=20 >> parameters?? >> > > Definitely yes. I-Force also allows that. > Okay, will do so...also, is itme who has an outdated version of=20 input.h, or does it really not have ET Ramp, Damper, and Inertia?? And=20 what would FF_RUMBLE be?? Is it I-force specific?? If it's okay, I'll=20 add FF_RAMP, FF_DAMPER, and FF_INERTIA since they're defined in the=20 spec(5.1.1)... > > Anyway, we will have to change the API to take custom effects into > account. > Yes, I know...have you decided how we'll do that?? I guess that=20 since(in PID specs at least) custom effect data is sent on one(or more)=20 report by itself, saved in a memory position(just like an effect), etc.,=20 we could just make an IOCTL to upload the custom data, then we can=20 normally upload an effect which points to that custom data...that would=20 require only minor changes to the existing code... Rodrigo P.S.: I've started libff too...send me all ideas you have for nice=20 things it could do...I'm using re-usable parameter blocks(something like=20 FF_create_constant(float direction, float magnitude, FF_envelope=20 *envelope, FF_trigger *trigger, FF_time *time, FF_flags flags) ) --=20 ******************************* * Rodrigo Damazio * * *************************** * * cu...@uo... * * rod...@po... * * ICQ: #3560450 * * http://www.vros.com/cuddly/ * * *************************** * * Engenharia da Computa=E7=E3o * * Escola Polit=E9cnica * * USP - S=E3o Paulo * ******************************* |