On Tue, May 20, 2014 at 11:26 PM, Elias Vanderstuyft <elias.vds@xxxxxxxxx> wrote: > On Tue, May 20, 2014 at 10:58 PM, Michal Malý > <madcatxster@xxxxxxxxxxxxxxxxxx> wrote: >> On Tuesday 20 of May 2014 16:16:12 simon@xxxxxxxxxxxxx wrote: >>> Regarding the question of emulated vs. real effects, can we extend the API >>> so that applications can know which effects are really supported, and >>> enable/disable emulation somehow? >> >> I suppose that a few extra flags (FF_PERIODIC_EMULATED etc.) defined in >> "uapi/linux/input.h" should suffice. > > @Dmitry: > Now that we're talking about API changes, I would like to propose some > additional things in the Linux FF API: > > - Possibility to *get* FF state variables, such as the value of the > current GAIN, and the current AUTOCENTER: > At the moment, only *setting* is possible. > This poses a problem when implementing proper AUTOCENTER state > recovery (upon closing a Windows program) in Wine, because the initial > AUTOCENTER state was unknown. > The same applies for GAIN. > > - Introduce multiple types of GAIN, apart from the current global > GAIN, e.g. GAIN_CONSTANT and GAIN_DAMPER: > This is mainly on request of some users, especially Logitech users: on > Windows Logitech additionally supports to set the global Damper and > Spring gain. > Maybe it would be nicer to create a global gain for every supported > Linux FF effect? And Roland Bosa (from Logitech) also agrees with the following addition/modification to the Linux FF API: - Infinite iterations, or in Linux FF terms: playback of an effect with an event count of infinity. Right now, an event count of zero stops the effect, while the maximum count is INT_MAX. An event count value of '-1' can be used to indicate infinity. (However note that it is somewhat inconsistent with the infinite effect "duration" we already support: in that case '0' is used) Is this feasible? (in terms of backward compatibility) Thanks, Elias -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
