On 11/17/10 22:26, Max Schwarz wrote:
> I would propose specific methods for changing the resolution, axes ranges,
> etc., and one final call to send out events.
Sounds fine.
Simon
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.
On Wednesday 17 November 2010 at 23:55:20, Simon Thum wrote:
> > if possible, wrap it. it's much easier to work around issues than when
> > each driver just mangles the struct directly. But I don't think you need
> > a new call here, just re-using the existing InitValuatorAxisStruct
> > should do.
On 11/14/10 22:52, Peter Hutterer wrote:
> On Sun, Nov 14, 2010 at 06:51:43PM +0100, Max Schwarz wrote:
Are the drivers "allowed" to access the valuator structure
(e.g. dev->valuator->axis[0].resolution = XY) or should I implement
wrapper functions in the server to do that?
>>>
>>> I
Hi,
I implemented most of the dynamic-resolution feature today.
Patches are at https://github.com/x-quadraht/pscroll/tree/master/patches/ .
The wheel resolution property now resides in the emuWheel.c code, which
reflects that it only affects wheel emulation. I added a manpage entry, too.
Curren
On Sun, Nov 14, 2010 at 06:51:43PM +0100, Max Schwarz wrote:
> Hi Simon,
>
> > > The clients depend on XIDeviceChangedEvents anyway to acquire the new
> > > resolution when the user switches input devices (see pscrolltest.c).
> >
> > Though that sounds fine, I think the event is intended for mast
Hi Simon,
> > The clients depend on XIDeviceChangedEvents anyway to acquire the new
> > resolution when the user switches input devices (see pscrolltest.c).
>
> Though that sounds fine, I think the event is intended for master/slave
> issues. That's deep in spec land, however. Read up and see if
On 11/14/10 00:18, Max Schwarz wrote:
> My proposal would be to make an XINotifyDeviceChanged(DeviceIntPtr dev)
> function available to the drivers. It would simply copy the values from the
> device to a DeviceChangedEvent and send it via XISendDeviceEvent().
> Such a function could also replace
Hi Simon,
> Still, the 42 is a bit odd.
Caught me ;-)
The value was a lucky guess, but it works pretty well for me (I'm using a
TrackPoint to test it, other devices might yield other values...)
> Towels anyone?
No Bugblatter Beast in sight, so I'm safe for now ;-)
> I guess that's mostly Peter
On 11/08/10 22:55, Max Schwarz wrote:
> Hi Simon,
>
>> That sounds fine. But how are button events being generated which match
>> a potential only-smooth-scrolling input?
> I'm not sure I understand your question. I didn't change the generation of
> button events in any way. They are just emitted
On 11/09/10 06:07, Peter Hutterer wrote:
> I don't understand the no_integration stuff. aside from it being a bit of a
> misnomer, I'm missing the point of what is supposed to do. if the axis is in
> relative mode, you can go past the axis ranges anyway. In absolute mode,
> well, are wheels ever in
On Sun, Nov 07, 2010 at 02:56:22PM +0100, Max Schwarz wrote:
> I finally found some time for smooth scrolling.
> I've got rebased patches against git versions for
> xserver, xf86-input-evdev, xf86-input-synaptics
> in my github repo at https://github.com/x-quadraht/pscroll.
>
> Would you mind chec
Hi Simon,
> That sounds fine. But how are button events being generated which match
> a potential only-smooth-scrolling input?
I'm not sure I understand your question. I didn't change the generation of
button events in any way. They are just emitted in parallel by the old code.
> > You want that
On 11/07/10 18:03, Max Schwarz wrote:
> Hi Simon,
>
>> A thing I'm
>> missing is how you're establishing the relationship of smooth and button
>> scrolling? It might just be me since I'm only looking at the diffs.
> It's certainly subtle ;-)
> Look at EvdevProcessRelativeMotionEvent().
> In case o
Hi Daniel,
> Nice!
Thanks ;-)
> I think the NoIntegration stuff is entirely unnecessary though -
> if you've set your axis range appropriately, then you won't need this
> hack at all. If you can come up with a patchset that doesn't require
> this, I'd be more than happy to test it with Synaptics
Hi Simon,
> A thing I'm
> missing is how you're establishing the relationship of smooth and button
> scrolling? It might just be me since I'm only looking at the diffs.
It's certainly subtle ;-)
Look at EvdevProcessRelativeMotionEvent().
In case of a change on REL_(H)WHEEL the clicks are queued an
Hi,
On Sun, Nov 07, 2010 at 02:56:22PM +0100, Max Schwarz wrote:
> I finally found some time for smooth scrolling.
> I've got rebased patches against git versions for
> xserver, xf86-input-evdev, xf86-input-synaptics
> in my github repo at https://github.com/x-quadraht/pscroll.
>
> Would you mind
On 11/07/10 14:56, Max Schwarz wrote:
> Hi,
>
> I finally found some time for smooth scrolling.
Great news, thanks for your efforts!
> I've got rebased patches against git versions for
> xserver, xf86-input-evdev, xf86-input-synaptics
> in my github repo at https://github.com/x-quadraht/pscroll.
>
Hi,
I finally found some time for smooth scrolling.
I've got rebased patches against git versions for
xserver, xf86-input-evdev, xf86-input-synaptics
in my github repo at https://github.com/x-quadraht/pscroll.
Would you mind checking them and telling me what needs to be done to get them
merged?
18 matches
Mail list logo
