Looking at the libinput code and docs, it gives conflicting answers as to what "flat acceleration" means. In the code it kind of looks like "flat acceleration" means "zero acceleration with constant velocity multiplier".
Please check my findings but I think this means LIBINPUT_CONFIG_ACCEL_PROFILE_FLAT is incorrectly named and perhaps in most profiles there is zero acceleration in the physical sense. So more accurate names would be:
MirPointerAcceleration -> MirPointerSpeed
mir_pointer_acceleration_none -> mir_pointer_speed_native
mir_pointer_acceleration_constant -> mir_pointer_speed_constant (with bias 0 same as native?)
mir_pointer_acceleration_adaptive -> mir_pointer_speed_accelerated
Sorry to be pedantic, but it's libinput that has apparently confused the physics terminology. We should try not to copy their mistakes, if they are mistakes...
Looking at the libinput code and docs, it gives conflicting answers as to what "flat acceleration" means. In the code it kind of looks like "flat acceleration" means "zero acceleration with constant velocity multiplier".
Please check my findings but I think this means LIBINPUT_ CONFIG_ ACCEL_PROFILE_ FLAT is incorrectly named and perhaps in most profiles there is zero acceleration in the physical sense. So more accurate names would be:
MirPointerAcc eleration -> MirPointerSpeed acceleration_ none -> mir_pointer_ speed_native acceleration_ constant -> mir_pointer_ speed_constant (with bias 0 same as native?) acceleration_ adaptive -> mir_pointer_ speed_accelerat ed
mir_pointer_
mir_pointer_
mir_pointer_
Sorry to be pedantic, but it's libinput that has apparently confused the physics terminology. We should try not to copy their mistakes, if they are mistakes...