On Tue, Sep 09, 2008 at 11:24:48AM +0200, Florian Echtler wrote:
we're currently trying to control multiple X pointers through XTest.
Moving them using XTestFakeDeviceMotionEvent works as expected; however,
sending a button event using XTestFakeDeviceButtonEvent doesn't.
In fact, the test
On Tue, Sep 16, 2008 at 11:20:01PM +0200, Mildred Ki'Lya wrote:
I have a macbook, and a while ago (May 2008, when synaptics wasn't
included in the Xorg project), I made a patch in order to improve
usability of touchpad with one mouse button only.
Thanks! The patch had been applied as
On Wed, Sep 17, 2008 at 08:38:09PM -0400, Chuck Robey wrote:
I don't know if this is important or not, and I won't harp on this, but I've
heard before that an attempt is made both to keep evdev.c very current, AND to
have it not have anything in it that is Linux-only.
AFAIK, only the linux
On Wed, Sep 17, 2008 at 09:26:08PM +0200, Simon Thum wrote:
Maybe evdev works better? I seems there is a problem when both absolute
AND relative axes are exposed,
The reason for this is that there's a couple of popular devices
(keyboard/mouse combos) that claim to have both relative x/y axes
On Thu, Sep 18, 2008 at 11:51:47PM -0500, Tobias Jakobi wrote:
After ioquake3 is started all keyb and mouse input stop. You can't move
the cursor, you can't click. Switching to another application isn't
possible, even switching to the VTs isn't possible.
All input is simply dead.
[...]
I
On Sat, Sep 20, 2008 at 11:48:08AM -0400, Chuck Robey wrote:
I myself really like the approach that xf86-input-joystick takes, it allows
the
approach that evdev takes for Linux, but it doesn't try to suppose that the
event interface that only works for Linux can work for other OSes. You know
On Sat, Sep 20, 2008 at 03:44:20PM -0700, Nikolay Karasev wrote:
My yesterday's update of Fedora 9 installed these updates
xorg-x11-drv-evdev version 2.0.4-1
xorg-x11-server-Xorg 1.5.0-1
xorg-x11-server-common 1.5.0-1
https://bugzilla.redhat.com/show_bug.cgi?id=456936#c19
Cheers,
Peter
According to Section 12.4 of the XKB Protocol Spec, if a key only has a single
group but the keyboard has multiple groups defined, the core description of
the key is a duplication of the single group across all symbols. i.e.
G1L1 G1L2 G1L1 G1L2 G1L3 G1L4 G1L3 G1L4
The previous code generated G1L1
On Fri, Sep 19, 2008 at 01:29:58PM +0200, Søren Hauberg wrote:
I do have a follow-up question (you can't get rid of me that easy :-)
). I have modified the 'usbtouchscreen' kernel module such that it can
use calibration parameters. With this in place, my touchscreen works
in X with the 'evdev'
On Tue, Sep 16, 2008 at 11:58:56AM +0200, Sascha Hlusiak wrote:
BTW: With MPX, having two key devices attached to the first master device
works fine, regarding the keymap. When creating a second master and attaching
a keyboard to that, key presses seem to use the keymap of the first master
Here's the (hopefully) final patches to device properties in the server.
As mentioned in [1], Configure/Query property functionality and requests have
been culled.
Patch 1 removes these requests. An updated inputproto is required as well of
course.
Patch 2 allows property handlers to return
From: Peter Hutterer [EMAIL PROTECTED]
Add delete parameter to SetProperty handler, handlers can refuse to delete a
property by returning something other than Success.
---
Xi/xiproperty.c| 20 ++--
dix/devices.c |6 +-
include/exevents.h |3 ++-
include
On Tue, Sep 23, 2008 at 02:41:16AM +, Jason Spiro wrote:
Problem: Many[1] users have killed X by accident.[2]
Solution idea: Make it harder to kill X by accident. E.g. you could
change the key sequence users must press.
* Maybe require Control+Alt+Backspace then Control-Alt-Y.[3]
On Tue, Sep 23, 2008 at 04:39:49AM +, Jason Spiro wrote:
Thanks for the info. 1. So I guess when using evdev, a way to implement my
Ctrl+Alt+Bksp then Ctrl+Alt+Y idea would be this?: Ctrl+Alt+Bksp should latch
some new modifier called ctrl_alt_bksp_was_pressed, and Ctrl+Alt+Y should zap
On Wed, Sep 24, 2008 at 02:42:29AM +0100, Simos Xenitellis wrote:
The next step in replacing xkbcomp would be to list any of the
structures we many want to eliminate or reduce some of the fields.
xkb_keymap
| xkb_keycodes
| xkb_types
| xkb_compatibility
|
On Wed, Sep 24, 2008 at 07:48:57AM +0200, Simon Thum wrote:
If deletable is FALSE, the prop can only be deleted by the server/a driver,
and even then only if all handlers agree.
That's a bit stricter than what I was looking for. If I want to delete a
prop in-server, I'd like be able to avoid
On Sat, Sep 27, 2008 at 06:10:32PM +0100, Magnus Kessler wrote:
Since updating to the current git version of xorg-server, inputproto and
xf86-input-synaptics I observe extra pointer movements for every event
generated by the touchpad.
Even when not touching the pad and using the buttons
On Sun, Sep 28, 2008 at 08:23:51AM +0100, Magnus Kessler wrote:
I have just reverted the part of commit
c405a69f83dab77cfe6c76f718a3ca5614a85918 that passes the actual x/y ranges
to xf86InitValuatorAxisStruct. Now the extra movement is gone, but I get a
somewhat quicker cursor movement
On Sun, Sep 28, 2008 at 10:09:01AM +0100, Magnus Kessler wrote:
The creation of the repeater fifo in the synaptics driver looks dubious. The
file mode should be ORed with the S_IFIFO flag and the dev parameter should
be null. The mknod(3p) man page suggests using mkfifo instead.
Agreed.
On Sun, Sep 28, 2008 at 03:11:46PM +0100, Magnus Kessler wrote:
Testing status against EEXIST is wrong and we should check errno instead if
we want to allow the use of an existing file. However, since we pass a file
name that in principle could be any existing file (not just fifos) is there
On Mon, Sep 29, 2008 at 09:42:22AM +0200, Søren Hauberg wrote:
I'm trying to differentiate touchpads from touchscreens in the evdev
driver. Both types of devices has absolute axis, and emit the
BTN_TOUCH signal. So, I need something else to tell them apart.
Unfortunately, I don't have access
Søren:
On Mon, Sep 29, 2008 at 01:29:35PM +0200, Søren Hauberg wrote:
Sorry, I wanted to suggest that in reply but missed it. Anyway, be aware
that as your patch is now, you're also triggering on absolute axes you can't
handle/don't know. I'd consider that a regression.
Ahh, I (think I)
file?
If not, xorg-drivername.pc or justdrivername.pc?
Cheers,
Peter
From 0351d0aad80b6400381b8e32a73228987fb38ab9 Mon Sep 17 00:00:00 2001
From: Peter Hutterer [EMAIL PROTECTED]
Date: Fri, 26 Sep 2008 10:42:05 +0930
Subject: [PATCH] Add evdev.pc for compiler flags if compiling with
evdev
On Mon, Sep 29, 2008 at 11:01:44PM +0100, [EMAIL PROTECTED] wrote:
@@ -79,7 +79,7 @@ miPointerScreenFuncRec g_winPointerCurso
static void
-winPointerWarpCursor (ScreenPtr pScreen, int x, int y)
+winPointerWarpCursor (DeviceIntPtr pDev, ScreenPtr pScreen, int x, int y)
{
On Tue, Sep 30, 2008 at 02:15:45PM +0200, Søren Hauberg wrote:
2008/9/29 Peter Hutterer [EMAIL PROTECTED]:
evdev already has the code for device properties in e.g. draglock.c. Best to
just check it but maybe wait a day or so, I have changes in the pipe that
restructure the use of DP
On Tue, Sep 30, 2008 at 08:04:50PM -0700, Dan Nicholson wrote:
Total nitpicking, but it's not necessary to add xorg-evdev.pc.in to
EXTRA_DIST since you added it to AC_OUTPUT in configure.ac. automake
takes into account files necessary for autoconf and adds them to
DIST_COMMON.
Nitpicking is
mutouch 1.2.0 has issues with the current X server as it does not handle
inverted axes (or handles them as inverted even when they aren't). This is
fixed now, and I have anecdotal evidence that it even works.
Peter Hutterer (6):
Check for XINPUT ABI 3.
Remove trailing whitespaces
On Thu, Oct 02, 2008 at 10:12:40AM +0100, Colin Guthrie wrote:
I'm using xf86-input-synaptics-0.15.2 and wonder if other users have a
problem with the scroll zone after resuming from suspend.
For me it just stops working which is pretty annoying. Does anyone know
how to help diagnose
On Wed, Oct 01, 2008 at 11:45:03AM +0200, Søren Hauberg wrote:
Good point. Perhaps the recently added 'invert_[x|y]' options in the
evdev driver should be removed? Perhaps not, as such an option might
be generally usable.
I think it is a feature worth having. The cost of maintainance is low
On Tue, Sep 30, 2008 at 02:44:26PM +0100, John Tapsell wrote:
I have a device without a keyboard, but I still send keyboard events
to X. Specifically I use synergy.
what version of X are you running?
Is there a way to add some sort of 'virtual' keyboard?
X server 1.4 and above always have
On Thu, Oct 02, 2008 at 12:44:29PM +0100, Colin Guthrie wrote:
Now what to do I wonder... as /dev/input/event2 does actually exist.. I
wonder if it's a timing thing?
It probably is. I don't know how to get around that though other than adding
the synaptics options to your fdi file and letting
The current code exposes to inconsistent updates, i.e. if handler N succeeds
but handler N+1 fails in setting the property, an error is returned to the
client although parts of the server now behave as if the property change
succeeded.
This patch adds a checkonly parameter to the SetProperty
On Wed, Oct 08, 2008 at 08:11:26AM +0200, Simon Thum wrote:
Peter Hutterer wrote:
The current code exposes to inconsistent updates, i.e. if handler N succeeds
but handler N+1 fails in setting the property, an error is returned to the
client although parts of the server now behave
On Tue, Oct 07, 2008 at 11:48:14PM +0200, Søren Hauberg wrote:
Okay, just wasn't sure if I missed anything. I had a little time to
test today, and things didn't work that well for me. I tried using the
parameters (min_x, max_x, ...) that worked with my original patches,
and evtouch, and they
On Wed, Oct 08, 2008 at 09:12:44AM +0200, Simon Thum wrote:
Peter Hutterer wrote:
Axis range changes are one example I can think of. The driver needs to
update
it for axis inversion, the server for scaling.
Hmm - that essentially forbids moving inversion into the server (which
could
On Thu, Oct 09, 2008 at 03:20:36AM +0200, Simon Thum wrote:
So your point is to never have properties in the driver that could be in the
server? This may be tough, as drivers have a quicker turnover time, and
features can get added easier.
Well, against double-handling a prop in general.
On Wed, Oct 08, 2008 at 06:59:33PM +0200, Clemens Eisserer wrote:
The XKEYBOARD keymap compiler (xkbcomp) reports:^M
Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols^M
Ignoring extra symbols^M
Errors from xkbcomp are not fatal to the X server^M
You can
On Thu, Oct 09, 2008 at 11:41:27PM +0100, Magnus Kessler wrote:
The attached patch lets git ignore pkgconfig files.
Thanks, pushed.
Cheers,
Peter
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
On Thu, Oct 09, 2008 at 03:42:50PM +0200, Simon Thum wrote:
One non-ignoring handler is invoked at max. For this we have to
differentiate the RC.
When a handler is invoked, it may decide to call a new function which
allows it to pass through to handlers AFTER itself. A logical complement
On Fri, Oct 10, 2008 at 09:04:58PM +1100, William Grant wrote:
TRUE was not replaced with Success when all of the other property
handler return codes were. This meant that properties ended up set in
the driver but not the rest of the server.
Pushed as db6e631d31d4ffd476ccd105f8adb8d8b4727b29.
On Sat, Oct 11, 2008 at 03:27:48PM +0100, Colin Harrison wrote:
There is a double up of some code in dix/events.c, function
ReleaseActiveGrabs(), that may give
trouble?
at about line 1920
if (dev-deviceGrab.grab SameClient(dev-deviceGrab.grab,
client))
{
On Fri, Oct 10, 2008 at 11:54:56AM +0200, Simon Thum wrote:
If so, a few questions:
- A handler that registers at the head of the queue, assumes it is before
other handlers. Thus it has to be aware of other handlers in the first
place?
Yes, that would be the uncommon case, in which we
On Sun, Oct 12, 2008 at 06:17:20PM +0200, Simon Thum wrote:
Peter Hutterer wrote:
The patch I proposed does not make any guarantee over when a handler is
called. This automatically separates handlers so they cannot interfere with
each other, and dependency ordering is a nonissue, as you
On Tue, Oct 14, 2008 at 02:16:22PM +0200, Erik Streb del Toro wrote:
When I have “implies”¹ in my xkbmap it produces not the expected
U+21D2 RIGHTWARDS DOUBLE ARROW
as described in the comment of keysymdef.h but the symbol
U+22A2 RIGHT TACK
But this only in KDE apps not in Gnome/GTK. But
On Mon, Oct 13, 2008 at 04:35:37PM +0200, Andre Herms wrote:
Attached is a patch for the syndaemon of the synaptics driver. It
prevents the
polling of the keyboard state. Instead it uses the XRecord extension of
the
Xserver for an event triggered notification of key events. Of
They are stored in floats, so we might as well take them like they are. Plus,
this way keith's mouse can be configured to his liking.
Spotted by Keith Packard.
---
hw/xfree86/common/xf86Xinput.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Thu, Oct 16, 2008 at 11:10:39PM +0200, Tobias Jakobi wrote:
The problem: When starting/restarting the xserver the mousewheel does not
work. Investigating with xev reveals that the wheel generates button events
6 and 7.
How to get the mouse working: Unplug and replug the device, then the
Julien Cristau (1):
Set pInfo-fd to -1 on DEVICE_CLOSE
Peter Hutterer (3):
Fix Device reopened after N attempts message.
Don't post keycodes 255.
evdev 2.0.7
git tag: xf86-input-evdev-2.0.7
http://xorg.freedesktop.org/archive/individual/driver/xf86-input-evdev-2.0.7
platforms.
Peter Hutterer (55):
No need to finalize MB emulation after EvdevProbe anymore.
Bump to 2.0.99.
Count buttons at probe and print to log.
Remove EvdevConvert, nobody calls it now anyway.
Remove stale comments.
Update COPYING with the correct copyright info
On Thu, Oct 16, 2008 at 01:10:03PM +0100, [EMAIL PROTECTED] wrote:
Apparently we shouldn't need this, something else is wrong...
no, I was wrong in the previous email, confusing the intention of the code
here. Am I right that this is the interface between X and the windows API?
In that case
If HAL is restarted, the device list is send to the server again, leading
first to duplicate devices (and thus duplicate events), and later to a
FatalError Too many input devices.
dev-config_info contains the UDI for the device. If the UDI of a new devices
is equal to one we already have in the
On Sat, Oct 18, 2008 at 07:50:38AM +0800, Sam Spilsbury wrote:
I'm continuing Peter Hutterer's MPX aware version of compiz and
extending it to all of compiz-fusion. Some of the plugins use a call
to XFixes to get a cursor image for the current cursor and to hide the
current cursor. I didn't
it and RAW mode is never set.
So let's simply set it to TRUE as default, since that's what it is by default
anyway (AutoAddDevices and AutoEnableDevices are true by default).
And while we're at it, switch the rest of the defaults over to named
intializers.
Signed-off-by: Peter Hutterer [EMAIL
Peter Hutterer (7):
Remove trailing whitespaces.
Remove XFREE_V4 define and all code that expects it to be unset.
Remove RCS tags.
Fix build, xf86Version.h - xorgVersion.h
Add Option Model to supported list of options.
Add special handling for Sunit dSeries. RH
On Fri, Oct 17, 2008 at 05:33:33PM -0700, Philip Langdale wrote:
I've attached example fdi and callout script implementations (the
vmmouse-detect
binary that is referred to is debian/ubuntu specific but that can be folded
into
a hald-probe style binary or bundled elsewhere if desired)
So,
On Fri, Oct 17, 2008 at 08:23:32AM +0200, Andre Herms wrote:
Thanks for the patch! There's a number of irrelevant white-space changes in
that patch. Can you please clean it up and re-send it? Thanks.
Sorry, my mistake.
I removed the whitespace changes and further added a a small change
On Thu, Oct 23, 2008 at 02:13:05PM +0200, Xavier Bestel wrote:
it seems anonymous git is broken right now:
fatal: read error (Connection reset by peer)
the server is dead. or out for a beer. one of the two.
Cheers,
Peter
___
xorg mailing list
Bastien Nocera (1):
Keysyms needed for some HID remote controls to work under X. #16519
James Cloos (2):
fix typo in commit 40ed4eef
Add dead_perispomeni to keysymdef.h
Peter Hutterer (5):
Add keysyms for XF86XK_Battery, XF86XK_Bluetooth, XF86XK_WLAN, XF86XK_UWB
On Fri, Oct 24, 2008 at 11:43:03AM +0200, Søren Hauberg wrote:
Yeah, I can understand that. As I think I've made quite clear in
previous posts: I'm stupid. That is, I don't really know X. So, here's
a stupid question [1]: the server scales from what ever the driver
reports to some range. So,
On Sat, Oct 25, 2008 at 01:42:31PM +0100, Colin Guthrie wrote:
Well they didn't appear to come up I'll have a look and see if I can
get more info. Not being able to log in to debug it due to lack of
keyboard meant I didn't really research/probe as much as I should have
done... :)
lshal
On Sat, Oct 25, 2008 at 02:22:03AM -0400, James Cloos wrote:
Peter == Peter Hutterer [EMAIL PROTECTED] writes:
Peter diff --git a/src/xlibi18n/imKStoUCS.c b/src/xlibi18n/imKStoUCS.c
Peter index 83c1483..4b4f628 100644
Peter --- a/src/xlibi18n/imKStoUCS.c
Peter +++ b/src/xlibi18n
At the moment, we have the following keysyms defined to put a computer into a
sleep state:
XF86XK_Standby0x1008FF10 /* System into standby mode */
XF86XK_PowerDown 0x1008FF21 /* Deep sleep the system */
XF86XK_Sleep 0x1008FF2F /* Put system to sleep*/
Proposed
On Mon, Oct 27, 2008 at 08:44:24AM +0100, Søren Hauberg wrote:
Just a quick thought: double-scaling means we transform one coordinate
from [a, b] to [c, d] in the driver, and then from [c, d] to [e, f] in
the server, right? Here [a, b] is determined by the hardware. What if
we choose [c, d]
On Mon, Oct 27, 2008 at 01:23:03PM -0400, Drew Ogle wrote:
(II) 3Dconnexion SpaceNavigator: Found x and y relative axes
(WW) 3Dconnexion SpaceNavigator: Don't know how to use device
that probably just means that it doesn't expose buttons. what's the output of
evtest when you point it at the
On Mon, Oct 27, 2008 at 09:20:55AM +0100, Søren Hauberg wrote:
Yes, not knowing [a, b] at server startup is indeed the real problem.
If we want to support run-time calibration, then it simply won't be
possible to fix these parameters at startup. From what I understand,
it is only the driver
with negative button numbers after
trying to map BTN_0.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
src/evdev.c | 27 +++
src/evdev.h |2 +-
2 files changed, 24 insertions(+), 5 deletions(-)
diff --git a/src/evdev.c b/src/evdev.c
index cc072d8..9ef2829 100644
Some devices require run-time axis calibration. We can't change the min/max
ranges once we've initialised the valuator structs though, so in-driver
run-time calibration is required.
If the property is set, the driver scales from the calibrated range to the
values reported to the X server (which
Last set of features added, including run-time calibration and axes swapping.
Peter Hutterer (9):
emulate MB: fix confusing log message.
Fix axis inversion for absolute coordinates.
emuMB: add EvdevMBEmuOn and call from EvdevOn to register wakeup handlers.
Flush input
this one here, quick test shows it works:
From b783944ac784c42ba84b3dfe77d60107b9581a30 Mon Sep 17 00:00:00 2001
From: Peter Hutterer [EMAIL PROTECTED]
Date: Tue, 4 Nov 2008 15:27:30 +1030
Subject: [PATCH] mi: clean up mieqProcessInputEvents, copy all events before
processing.
Copy the EventRec's
you suggested. To make
the flow cleaner, I moved all the EQ and memory alloc stuff together and the
copies into local variables below it.
From 218f4664a032a8096d576ab8a43f33226007b6a4 Mon Sep 17 00:00:00 2001
From: Peter Hutterer [EMAIL PROTECTED]
Date: Tue, 4 Nov 2008 15:27:30 +1030
Subject
On Wed, Oct 29, 2008 at 08:51:24AM +0100, Florian Echtler wrote:
a while ago, after the MPX merge, there was a brief discussion about
multipointer support for userspace. I'd like to revive this discussion,
and I have some bits to restart it:
- At http://tisch.sf.net/ , you can find the first
-u.master :
NULL;
From 7693b94cd08030b9668130410104f432162f2859 Mon Sep 17 00:00:00 2001
From: Peter Hutterer [EMAIL PROTECTED]
Date: Tue, 4 Nov 2008 15:27:30 +1030
Subject: [PATCH] mi: clean up mieqProcessInputEvents, copy all events before
processing.
Copy the EventRec's information into local
On Tue, Nov 04, 2008 at 07:21:50PM -0500, Saist wrote:
What I don't know is whether or not such an interface program could be
designed under Linux to begin with... X.org documentation confuses the
living daylights out of me, so I don't really know if the X.org input system
could support
On Sat, Nov 08, 2008 at 08:53:24PM +0100, Mildred Ki'Lya wrote:
patch 1
Option Orientation integer
patch 2
Option DontReportSize boolean
patch 3
Option VertSpeed float
Option HorizSpeed float
please split the patch into 3 separate patches as grouped above. They
On Tue, Nov 11, 2008 at 01:27:34PM +0100, Mildred Ki'Lya wrote:
Well, I don't really know how to creates patch series using git. It was
easier for me to create a repository I made available on github:
git://github.com/mildred/xorg-synaptics-orientation-patch.git
On Tue, Nov 11, 2008 at 09:42:52PM +0100, Andre Herms wrote:
Sorry for the long delay. I was waiting for the git head to get in a
consistent state without the ugly Xrecord patch (version 1).
Thanks. Please submit your patch as a git commit (git-format-patch HEAD^)
though so it can be quickly
From: Peter Hutterer [EMAIL PROTECTED]
We need them for each window, every time a window is allocated. Storing them
in a devPrivate is the wrong thing to do.
This also removes the unused ENTER_LEAVE_SEMAPHORE_ISSET macro.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/events.c
On Thu, Nov 13, 2008 at 05:40:20PM -0600, Robin Cook wrote:
I am using evdev.
Section InputDevice
Identifier Keyboard0
Driver kbd
Option XkbModel evdev
Option XkbLayout us
Option XkbVariant dvorak
Option XkbRules
On Fri, Nov 14, 2008 at 12:44:20AM +0100, Matija Šuklje wrote:
I noticed that when I unplug my USB mouse and later plug it back in, it
doesn't work in X anymore/again.
devices configured in the xorg.conf are not hotplug-capable.
An odd workaround I found and use now is that it works if
On Thu, Nov 13, 2008 at 11:56:09PM +, Clarke Wixon wrote:
Device 'Touchkit HID-USB Touchscreen':
Device Enabled:1
Middle Button Emulation:2
Middle Button Timeout:50
Wheel Emulation Inertia:10
Wheel Emulation:0
Wheel
, ignore pkgconfig .pc files
Convert last remaining ErrorF to xf86Msg
Peter Hutterer (8):
Adjust to new property API.
Install synaptics-properties.h in xorg include path, install
xorg-synaptics.pc.
man: typo fix.
man: Document multifinger-scrolling defaults.
man
From: Peter Hutterer [EMAIL PROTECTED]
Preparation for the new core enter/leave model.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/Makefile.am |2 +
dix/enterleave.c | 138 ++
dix/enterleave.h | 53
From: Peter Hutterer [EMAIL PROTECTED]
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/events.c| 15 ---
include/input.h |1 -
2 files changed, 0 insertions(+), 16 deletions(-)
diff --git a/dix/events.c b/dix/events.c
index 1ac45e3..eff7eeb 100644
--- a/dix
From: Peter Hutterer [EMAIL PROTECTED]
Device events always need to be delivered, core events only in some cases.
Let's keep them completely separate so we can adjust core event delivery.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/enterleave.c | 76 +++---
dix
From: Peter Hutterer [EMAIL PROTECTED]
FirstPointerChild: Return the first child that has a pointer within its
boundaries.
FirstPointerAncestor: return the first ancestor with a child within its
boundaries.
These are required for the updated enter/leave model.
Signed-off-by: Peter Hutterer
From: Peter Hutterer [EMAIL PROTECTED]
---
include/input.h |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/include/input.h b/include/input.h
index 5377d23..c78f0b7 100644
--- a/include/input.h
+++ b/include/input.h
@@ -97,12 +97,6 @@ SOFTWARE.
#define
From: Peter Hutterer [EMAIL PROTECTED]
These replace the ENTER_LEAVE_SEMAPHORE_* macros. Unused currently.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/enterleave.c | 38 ++
1 files changed, 38 insertions(+), 0 deletions(-)
diff --git a/dix
On Fri, Nov 14, 2008 at 01:13:16PM -0800, Keith Packard wrote:
I volunteered to manage an X server 1.6 release, tentatively scheduled
for the end of the year (yes, this year, 2008). This release will
include DRI2 and RandR 1.3 support. I'd like to know how much of the new
Xinput stuff will be
On Fri, Nov 14, 2008 at 02:08:12PM +0100, (none) wrote:
I'm using Xorg 1.4.2, and when I unplug my Logitech mouse from my
laptop, X restarts and brings me back to the xdm login screen.
I tried both the evdev and the mouse driver, with the same result (chose
to stay with mouse for now as I
On Sun, Nov 16, 2008 at 05:52:53PM -0800, Jeremy Huddleston wrote:
The keyboard mostly works, but it would probably be better if it were
treated as sun6... I just use the old-fashioned keyboard driver with:
Option XkbModelsun6
I looked through the xf86-input-evdev source, but I didn't
On Sat, Nov 15, 2008 at 10:38:33PM +0100, Matija Šuklje wrote:
New problems:
* button mapping for the mouse now works neither in KDE, nor KDM nor Fluxbox
* 'xev' now doesn't even recognise the HWheel buttons (evtest does though)
* synaptics driver using HAL ignores pretty much all the options
acceleration */
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
Cheers,
Peter
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
On Mon, Nov 17, 2008 at 11:25:25AM -0800, Dan Nicholson wrote:
I decided to take a crack at moving xkbcomp into the server so it's
not popen'd whenever a keymap is loaded. For the first crack, I'm
trying to just leave xkbcomp pretty much unchanged except for the
interface. What's causing me
On Tue, Nov 18, 2008 at 10:03:57AM +, Richard Hughes wrote:
On Mon, 2008-10-27 at 16:36 +1030, Peter Hutterer wrote:
At the moment, we have the following keysyms defined to put a computer into
a
sleep state:
XF86XK_Standby0x1008FF10 /* System into standby mode
On Tue, Nov 18, 2008 at 03:44:32AM -0800, Dan Nicholson wrote:
I agree completely. As soon as I looked at the path taken in
XkbDDXNamesFromRules, I realized how insane it was that there were all
these conversions. I'm just moving one step at a time here, with the
first one being: leave the
On Tue, Nov 18, 2008 at 10:16:05PM +0800, Leandro Galvez wrote:
How do I use the X11 with /dev/uinput device which I plan to simulate
all the input devices like keyboard, mouse and touchpad? How do I create
the xorg.conf for this to properly work? Do I need an entry for each
Expect this to be the last evdev 2.0.x release.
Julien Cristau (1):
Fix TestBit() on 64bit
Peter Hutterer (1):
evdev 2.0.8
git tag: xf86-input-evdev-2.0.8
http://xorg.freedesktop.org/archive/individual/driver/xf86-input-evdev-2.0.8.tar.bz2
MD5: 7f9ace5bcca1427b0da40827a74cbc33
sent to the TTY. Other patches of interest [2-4] are recommended to
avoid duplicate events.
Consider the evdev 2.0 branch to be discontinued.
The shortlog since RC 3:
Fernando Carrijo (1):
Fix error message
Peter Hutterer (2):
Store device file's minor/major to avoid duplicate devices
These replace the ENTER_LEAVE_SEMAPHORE_* macros. Unused currently.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
The newly added HasOtherPointer() function is needed to provide correct
enter/leave event handling during active grabs.
dix/enterleave.c | 50
that this model requires CoreEnterLeaveEvent and DeviceEnterLeaveEvent to
be split and treated separately.
[1] http://lists.freedesktop.org/archives/xorg/2008-August/037606.html
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
This is the updated model that now caters for enter/leave events during
1 - 100 of 1086 matches
Mail list logo
