On Wed, 2010-04-07 at 12:58:11, Simon Thum wrote: > I'm unsure I get it. I assumed you were breaking up the 1:1 relation > between scroll button presses and your scroll valuator, such that the > valuator may work with much higher precision while button-scroll remains > working for apps unaware of the scroll valuator(s). Is that intended?
Yes, that's correct. But the relationship between the hardware axis and scroll valuator is defined by the driver, that's all I wanted to say. A scroll valuator unit as proposed by Eric (unit relative to old scroll wheel presses) is a good idea in my opinion. In that way the value is independant of screen resolution and font size, and toolkits can then decide how many pixels to scroll depending on those values. Max _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
