Jack Grigg

I have just added Linux support to https://github.com/openleap/PyLeapMouse using your library - thanks! I am now considering migrating PyLeapMouse to use PyUserInput completely. Most cases implemented there appear to be...

Unfortunately I am as unfamiliar with relative scrolling as you are. I have asked the PyLeapMouse maintainer to clarify. EDIT: As per the comments in issue above, this was just...

In case you didn't see on the other issue, here is some extra info about the PyLeapMouse scrolling code: > For OS X, we're using by-pixel scroll amounts (kCGScrollEventUnitPixel). I...

I have been doing some tests with X11 and fake_input, and X11 **does** support horizontal scrolling. Buttons 4/5 click up/down (as in existing code); buttons 6/7 click left/right. Haven't found...

And Windows also supports horizontal scrolling. Here are the MSDN docs for win32api.mouse_event() http://msdn.microsoft.com/en-us/library/windows/desktop/ms646260%28v=vs.85%29.aspx This explains how wheel clicks are represented in Windows as well (by a scroll amount of...

Okay, turns out that "Movement should be no larger than 10" **is** necessary for OSX, having now found CGEventCreateScrollWheelEvent in the OSX docs: https://developer.apple.com/library/mac/documentation/Carbon/Reference/QuartzEventServicesRef/Reference/reference.html#//apple_ref/c/func/CGEventCreateScrollWheelEvent (And it turns out that Mac...

Looks like it. From the CGEventCreateScrollWheelEvent docs (also pasting the bit about movement no larger than 10): > **Parameters** > [...snip...] > _wheelCount_ > The number of scrolling devices on...

From a usability perspective I think it's important that whatever interface is decided on has a standard definition of scroll amounts that is appropriately converted to the OS-specific amounts, so...