The integration of the code has some deficiencies which try to resolve here
mainly to make reuse of the code easier. Also, the new valuator masks are
now used by acceleartion, making things much more straightforward.
___
xorg@lists.freedesktop.org: X.Or
ATCH 3/5] xfree86: document pointer acceleration in xorg.conf.man
>
> ---
> hw/xfree86/doc/man/xorg.conf.man.pre | 44
> ++
> 1 files changed, 44 insertions(+), 0 deletions(-)
>
> diff --git a/hw/xfree86/doc/man/xorg.conf.man.pre
> b/hw/
:59 +0100
> Subject: [PATCH 3/5] xfree86: document pointer acceleration in xorg.conf.man
>
> ---
[...]
> +times slower. Use this for very accurate hit-the-pixel work.
> +.TP 7
> +.BI "Option \*qAccelerationScheme\*q \*q" string \*q
> +Selects the scheme, which is the unde
gt; Next, I added the possibility to change pointer feedback controls
>> through options. The InputClass stuff makes it more sensible to do this.
>> TBH, I never figured why it was limited to command line options.
>
> there's protocol requests to adjust this at runtime and t
postpone until I'm sure about that.
>> Next, I added the possibility to change pointer feedback controls
>> through options. The InputClass stuff makes it more sensible to do this.
>> TBH, I never figured why it was limited to command line options.
>
> there's protocol r
limited to command line options.
there's protocol requests to adjust this at runtime and those are the only
pointer-acceleration related ones supported in GUI configuration tools
today. so arguably it's not essential since we've gone for years without it.
also, aren't you try
InputClass stuff makes it more sensible to do this.
TBH, I never figured why it was limited to command line options.
Third, some whitespace style fixes. Nothing functional.
Last but not least, the documentation should now reflect reality wrt
pointer acceleration. Affects the xorg.conf.man and --
On Sun, Dec 20, 2009 at 10:51:28PM +0100, Simon Thum wrote:
> Gene Heskett wrote:
> > On Saturday 19 December 2009, Simon Thum wrote:
> >> Gene Heskett wrote:
> >>> I would tend to agree. With modern high resolution mice, I have often
> >>> wished I could set the gain to a below 1 condition. My m
+--
> >> 1 files changed, 7 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/man/xinput.man b/man/xinput.man
> >> index fbf445e..6705373 100644
> >> --- a/man/xinput.man
> >> +++ b/man/xinput.man
> >> @@ -39,7 +39,11 @@ Change
Gene Heskett wrote:
> On Saturday 19 December 2009, Simon Thum wrote:
>> Gene Heskett wrote:
>>> I would tend to agree. With modern high resolution mice, I have often
>>> wished I could set the gain to a below 1 condition. My mouse now uses
>>> about a 1" x1.35" area of the pad, to cover a 1680x1
Lorenz Ruhmann wrote:
> After alternating between the two schemes several times and repeating
> specific mouse strokes a few dozen times, I'm getting less and less
> convinced that there actually is a difference. Also, considering you say
> my settings are correct (I'm not using adaptive decelerati
t;> @@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
>> .PP
>> .TP 8
>> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
>> -Change the acceleration of \fIdevice\fP.
>> +Change the pointer acceleration (or feedback) parameters of \f
/xinput.man
> index fbf445e..6705373 100644
> --- a/man/xinput.man
> +++ b/man/xinput.man
> @@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
> .PP
> .TP 8
> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
> -Change the acceleration of \fIdevice\fP.
>
Simon Thum wrote:
>
> Essentially, you have done exactly the right thing. Please ensure you
> don't use adaptive deceleration, which would explain that.
>
> You might try using the default profile and xset m 1 0. Technically this
> is polynomial but flat, ruling out adaptive decel.
>
> If the inacc
Gene Heskett wrote:
> I would tend to agree. With modern high resolution mice, I have often wished
> I could set the gain to a below 1 condition. My mouse now uses about a 1"
> x1.35" area of the pad, to cover a 1680x1250 screen, so its way too fast for
> this user.
I'm not sure I got it. What
On Saturday 19 December 2009, Simon Thum wrote:
>Justin Piszcz wrote:
>> On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
>>> Is there a way to exactly reproduce this old behavior with the new code?
>>> I don't like to rely on a scheme that is kinda considered obsolete.
>
>[..]
>
>> Yes, this is VERY ann
Justin Piszcz wrote:
> On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
>> Is there a way to exactly reproduce this old behavior with the new code?
>> I don't like to rely on a scheme that is kinda considered obsolete.
[..]
> Yes, this is VERY annoying to me as well (all of the new acceleration
> method
Lorenz Ruhmann wrote:
> With the old pointer acceleration code (now lightweight scheme) my mouse
> cursor behaves perfectly with the following command:
>
> xset m 16/100 1
>
> Even for far and fast mouse movement I can accurately hit small objects.
>
> However, I'
of \fIdevice\fP.
+Change the pointer acceleration (or feedback) parameters of \fIdevice\fP.
+The xset(1) man page has more details. For X.Org Server 1.7
+and above, there are additional device properties pertaining to pointer
+acceleration. These do not replace, but complement the pointer feedback
+se
On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
> Hi,
>
> After quite some testing of the new predictable pointer code introduced
> with version 1.6 I have a question.
>
> My mouse is a Logitech MX 518 set to 1600 dpi via lomoco and using HAL.
>
> With the old pointe
Hi,
After quite some testing of the new predictable pointer code introduced
with version 1.6 I have a question.
My mouse is a Logitech MX 518 set to 1600 dpi via lomoco and using HAL.
With the old pointer acceleration code (now lightweight scheme) my mouse
cursor behaves perfectly with the
input.man
> +++ b/man/xinput.man
> @@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
> .PP
> .TP 8
> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
> -Change the acceleration of \fIdevice\fP.
> +Change the pointer acceleration (or feedback) param
Simon Thum wrote:
> Resending to include philip as xinput maintainer. xset doesn't have a
> dedicated maintainer. Alan?
>
> Peter Hutterer wrote:
> > On Thu, Dec 10, 2009 at 03:13:30PM -0800, Alan Coopersmith wrote:
> > > Peter Hutterer wrote:
> > > > On Thu, Dec 10, 2009 at 10:24:20PM +0100, Sim
Simon Thum wrote:
> Resending to include philip as xinput maintainer. xset doesn't have a
> dedicated maintainer. Alan?
The wording seems fine to me. The one suggestion I have for the xset
change is on formatting codes - when you're trying to start a new paragraph
in an nroff man page, use a lin
/xinput.man
index fbf445e..e322e05 100644
--- a/man/xinput.man
+++ b/man/xinput.man
@@ -39,7 +39,11 @@ Change the mode of \fIdevice\fP.
.PP
.TP 8
.B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
-Change the acceleration of \fIdevice\fP.
+Change the pointer acceleration (or f
On Fri, Dec 11, 2009 at 09:54:11AM -0500, Ross Vandegrift wrote:
> > I'm open to suggestions though, in particular, I'd like to know where
> > people look first when they seek this kind of information.
>
> When I installed xinput, the first thing I did was look at the man
> page. But it's nearly
t; for me - I've been waiting a long time to be able to individually
> adjust pointer acceleration per device. User comprehensible docs
> would be awesome.
_Could_ have had? You know it's possible since to do that since 1.6? Or
am I misreading your statement?
Anyway, the doc
nation. I'd be a definite
improvement.
All of my boxes have mice and pointsticks. My laptop also has a
touchpad. The xinput changes could have had real usability impacts
for me - I've been waiting a long time to be able to individually
adjust pointer acceleration per devi
hange the mode of \fIdevice\fP.
.PP
.TP 8
.B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
-Change the acceleration of \fIdevice\fP.
+Change the pointer acceleration (or feedback) parameters of \fIdevice\fP.
+The xset man page has more details. For X.Org Server 1.7
+and ab
On Thu, Dec 10, 2009 at 03:13:30PM -0800, Alan Coopersmith wrote:
> Peter Hutterer wrote:
> > On Thu, Dec 10, 2009 at 10:24:20PM +0100, Simon Thum wrote:
> >> +has more detials. For X.org 1.7
> > ^^^ typo ^^ X.Org X Server 1.7
>
> I missed that one. Our canonical writing style is
Peter Hutterer wrote:
> On Thu, Dec 10, 2009 at 10:24:20PM +0100, Simon Thum wrote:
>> +has more detials. For X.org 1.7
> ^^^ typo ^^ X.Org X Server 1.7
I missed that one. Our canonical writing style is the name of
the X server binary has a lowercase o ("Xorg"), but the name of
t
ing the software years after the wiki is
updated to cover new releases, migrated to different URL's, etc.
> +Change the pointer acceleration parameters of \fIdevice\fP. The xset man page
> +has more detials. For X.org 1.7
s/detials/details/
> +and above, there are additional device
an
> +++ b/man/xinput.man
> @@ -39,7 +39,10 @@ Change the mode of \fIdevice\fP.
> .PP
> .TP 8
> .B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
> -Change the acceleration of \fIdevice\fP.
> +Change the pointer acceleration parameters of \fIdevice\f
ce\fP.
.PP
.TP 8
.B --set-ptr-feedback \fIdevice\fP \fIthreshold\fP \fInum\fP \fIdenom\fP
-Change the acceleration of \fIdevice\fP.
+Change the pointer acceleration parameters of \fIdevice\fP. The xset man page
+has more detials. For X.org 1.7
+and above, there are additional device p
Hello,
Please see:
http://www.linux-archive.org/debian-user/370897-mouse-keyboard-no-longer-work-after-apt-get-dist-upgrade-testing.html
Is it possible to make the cursor equivalent to 'xset m 20/5 1' with the
new xorg server? I have tried many different HAL settings and the closest
I was able
Harald Dunkel wrote:
> Sorry, but I do want to skip pixels (for gaming only, as written
> before). I understand that somebody overloaded (abused?)
> threshold = 0 to provide a completely different acceleration
> characteristic. I would like to have the "classic" profile with
> a "simple" characteri
Simon Thum wrote:
> Hi,
>
> you may want to read this:
> http://www.x.org/wiki/Development/Documentation/PointerAcceleration
>
> It is geared towards development, but also contains a lot of end-user
> info as well.
>
It helped to understand some things better, but see below.
>> with a constant
Hi,
you may want to read this:
http://www.x.org/wiki/Development/Documentation/PointerAcceleration
It is geared towards development, but also contains a lot of end-user
info as well.
> with a constant acceleration (e.g. for gaming)? Something like
I'm not sure what you mean by 'constant accele
Hi folks,
Maybe a stupid question, but I haven't seen it answered anywhere:
How can I disable the mouse pointer threshold to get a fast mouse
with a constant acceleration (e.g. for gaming)? Something like
'xset m 3 0' doesn't work, AFAICS. 'xset m 1 0' does work, but this
is way too slow on a big
Hello all (on git xorg),
since I had to learn ruby anyway, and hello world was already written:
http://the-shoebox.org/apps/140
This is a prototypish gui for tweaking pointer acceleration, i.e. all
the goodness no other UI knows. It isn't in any way serious, and you'll
need shooes,
x/ptrveloc.c
@@ -29,9 +29,13 @@
#include
#include
#include
+#include
+#include
#include
#include
+#include
+
/*********
* Predictable pointer acceleration
*
@@ -52,8 +56,8 @@
* which returns an acceleration
41 matches
Mail list logo
