Re: Stairstep mouse motion

2013-10-30 Thread Alf Schlichting
On Sat, Oct 26, 2013 at 10:13:11PM +0600, Alexandr Shadchin wrote: On Fri, Oct 25, 2013 at 11:41:25AM +0100, Edd Barrett wrote: On Thu, Oct 24, 2013 at 10:33:22PM +0300, Henri Kemppainen wrote: What happens when priv-swap_axes is set, and the ax ay branch is taken along with the

Re: Stairstep mouse motion

2013-10-30 Thread Edd Barrett
On Tue, Oct 29, 2013 at 11:07:29PM +0600, Alexandr Shadchin wrote: Look good to me. However I've a concern about compatibility with NetBSD. The kernel change should be documented in the commit message for xf86-input-ws so that they can catch up with the kernel change before they update

Re: Stairstep mouse motion

2013-10-30 Thread Matthieu Herrb
On Tue, Oct 29, 2013 at 11:07:29PM +0600, Alexandr Shadchin wrote: Update diff (add small hack for NetBSD). Thanks. This (plus the kernel diff) is ok matthieu@. -- Alexandr Shadchin Index: ws.c === RCS file:

Re: Stairstep mouse motion

2013-10-29 Thread Alexandr Shadchin
On Sun, Oct 27, 2013 at 04:31:37PM +0100, Matthieu Herrb wrote: On Sat, Oct 26, 2013 at 10:13:11PM +0600, Alexandr Shadchin wrote: On Fri, Oct 25, 2013 at 11:41:25AM +0100, Edd Barrett wrote: On Thu, Oct 24, 2013 at 10:33:22PM +0300, Henri Kemppainen wrote: What happens when

Re: Stairstep mouse motion

2013-10-26 Thread Alexandr Shadchin
On Fri, Oct 25, 2013 at 11:41:25AM +0100, Edd Barrett wrote: On Thu, Oct 24, 2013 at 10:33:22PM +0300, Henri Kemppainen wrote: What happens when priv-swap_axes is set, and the ax ay branch is taken along with the wsWheelEmuFilterMotion() branch. Following continue another event is

Re: Stairstep mouse motion

2013-10-26 Thread Henri Kemppainen
From: Alexandr Shadchin Before (on example pms(4)): * user move mouse * pms(4) read state mouse and process it * pms(4) send dx, dy and buttons in wscons * wscons generate simple events * ws(4) reads one event and process it immediately After applying diff: * user move mouse * pms(4)

Re: Stairstep mouse motion

2013-10-25 Thread Edd Barrett
On Thu, Oct 24, 2013 at 10:33:22PM +0300, Henri Kemppainen wrote: What happens when priv-swap_axes is set, and the ax ay branch is taken along with the wsWheelEmuFilterMotion() branch. Following continue another event is processed and now the axes are swapped again (ax and ay were not reset

Re: Stairstep mouse motion

2013-10-24 Thread Edd Barrett
On Wed, Oct 16, 2013 at 11:45:34PM +0100, Edd Barrett wrote: Tested on my x230t and will continue to test. No regrssions noticed on relative pointing devices. OK? Anyone? I appreciate that I am probably the only one using OpenBSD on a tablet, but a looks OK and no regressions for relative

Re: Stairstep mouse motion

2013-10-24 Thread Henri Kemppainen
Tested on my x230t and will continue to test. No regrssions noticed on relative pointing devices. OK? Anyone? I appreciate that I am probably the only one using OpenBSD on a tablet, but a looks OK and no regressions for relative pointing devices would be great. What happens when

Re: Stairstep mouse motion

2013-10-16 Thread Edd Barrett
On Thu, Jul 18, 2013 at 09:23:00PM +0100, Edd Barrett wrote: After applying your diff: Touchpad: smooth lines. Nipple: smooth lines. Pen: jagged lines. I wonder if it is because the pen is an absolute pointing device. You probably need extra magic in the

Re: Stairstep mouse motion

2013-07-20 Thread Matthieu Herrb
On Mon, Jul 08, 2013 at 08:26:56PM +0300, Henri Kemppainen wrote: I do fear that with some devices your patch will collapse too many events and make it harder to follow small radius curves. Right, I did not consider this case. If this is a problem, perhaps the code could be changed

Re: Stairstep mouse motion

2013-07-18 Thread Edd Barrett
Hi, On Mon, Jul 08, 2013 at 08:26:56PM +0300, Henri Kemppainen wrote: Here's a diff that does just that. If ws receives more than one delta along an axis, it will not sum these; each will go in a separate event. But if it gets an X delta followed by an Y delta (or vice versa), these will be

Re: Stairstep mouse motion

2013-07-08 Thread Henri Kemppainen
The issue that input drivers devices need high refresh frequency to be able to achieve high-precision freehand drawing is quite well known┬╣. Yes. But the bug here isn't about that. I think I'll have to elaborate a little. When you move the mouse, it will report its motion in an event with a

Re: Stairstep mouse motion

2013-07-08 Thread Henri Kemppainen
I do fear that with some devices your patch will collapse too many events and make it harder to follow small radius curves. Right, I did not consider this case. If this is a problem, perhaps the code could be changed to only collapse a pair of DELTA_X and DELTA_Y events, but never more

Stairstep mouse motion

2013-07-07 Thread Henri Kemppainen
So I needed to see my thoughts on paper but my desk was so full of stuff I couldn't make room for pen and paper. Instead I fired up Gimp, and drawing with the mouse worked fine until I realized it's next to impossible to draw diagonal lines that look like lines. Instead of straight lines, I got

Re: Stairstep mouse motion

2013-07-07 Thread patrick keshishian
On Sun, Jul 7, 2013 at 12:22 PM, Henri Kemppainen ducl...@guu.fi wrote: So I needed to see my thoughts on paper but my desk was so full of stuff I couldn't make room for pen and paper. Instead I fired up Gimp, and drawing with the mouse worked fine until I realized it's next to impossible to