On Sun, Sep 07, 2008 at 04:13:18PM +0200, Tomas Carnecky wrote:
> Peter Hutterer wrote:
> > On Sat, Sep 06, 2008 at 05:15:51PM -0700, Keith Packard wrote:
> >> On Sat, 2008-09-06 at 17:23 +0300, Daniel Stone wrote:
> >>
> >>> Isn't this just Prop
Following XDS, various notes, the discussions and preliminary executive
decisions by me, here's a first draft of XI2 features. If you have anything to
add, please speak up.
Time-line: I'd like to get it into server 1.6 but it doesn't look particularly
likely. 7.5 is more likely.
- Compatibility w
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 tes
On Mon, Sep 08, 2008 at 11:19:21AM +0200, Simon Thum wrote:
> Peter Hutterer wrote:
>> The difference to the current implementation is that there is no
>> meta-information about the property. This information included immutable,
>> client-created, range and pending. I deem
On Wed, Sep 10, 2008 at 10:10:09AM +, Wayne wrote:
> If I want my system to have MPX, can I just upgrade my system
> from xorg-server-1.5.0.tar.gz, or I still have to upgrade from
> git version?
mpx won't be in a released version until server 1.6 or possibly 1.7.
Cheers,
Peter
_
On Wed, Sep 10, 2008 at 04:57:57PM +0200, Sascha Hlusiak wrote:
> Hi Peter,
>
> > Commit against master at e622b00f...:
> > commit c57a7b463fb86d065fc6fe316ed25f302d51e5c6
> > Author: Peter Hutterer <[EMAIL PROTECTED]>
> > Date: Wed Sep 10 23:37:27 2008 +0
On Wed, Sep 10, 2008 at 05:55:58PM +0200, Sascha Hlusiak wrote:
> I'm asking because of the joystick driver that I maintain and that at
> the moment claims to be XI_MOUSE as well. Should I rather change it to
> "JOYSTICK", define a new atom for that or make it even configurable? I
> still don't kno
On Thu, Sep 11, 2008 at 09:29:45AM +0200, Roderick Colenbrander wrote:
> I'm still not clear which one will provide the exact events from the device?
> Relative events doesn't mean the device events. If this is pointer events,
> then it won't help. Pointer gets stuck on the border of the screen. Bu
On Thu, Sep 11, 2008 at 08:44:01PM +0200, Sascha Hlusiak wrote:
> > I'd say XI_MOUSE is wrong. JOYSTICK would be good, alternatively you could
> > also think about having JOYSTICK, GAMEPAD, and whatnot, although as the
> > XI_XYZ
> > atoms show too many aren't that great either.
> Isn't it more im
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 c32b4d4
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 06:46:17AM -0700, Hauberg wrote:
> Now, my problem is that X seems to somehow accelerate the output from the
> 'usbtouchscreen' module, so that when I move my finger to the left, the
> cursor moves about twice as far to the left as my finger did. This does not
> correspond
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 axe
On Fri, Sep 19, 2008 at 04:28:20AM +0700, Mikhail Gusarov wrote:
> Xi/chdevhier.h includes which is in libXi, but
> xserver configure script does not check for the libXi. Is it a bug?
Thanks, that's a bug. Fix pushed as cc20112a65d3f641ce0261c86a541f94fae5215c.
Cheers,
Peter
__
Just one fix - some kernels invalidate the device late after resume, leaving
us with dead devices. This issue is addressed by reopening the device if a
read error occurs.
Peter Hutterer (2):
Attempt to re-open devices on read errors.
evdev 2.0.5
git tag: xf86-input-evdev-2.0.5
http
On Fri, Sep 19, 2008 at 01:46:21PM +1000, Russell Shaw wrote:
> I built X from git. I get a stippled background when X starts but the
> mouse cursor is invisible. The mouse is working because i tested it
> with xev. I built and installed in this order:
commit e02f864fdf19a5ab1682336be343c57fdb69ef
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.
> [...
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 k
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
And here's the follow-up, to get rid of the group duplications. Note that
AFAICT, the protocol spec does not cover the case of xkb->core->xkb so we have
to do some guesswork here.
>From 82512610650f2695526d3b1f0c0a26e71ae02637 Mon Sep 17 00:00:00 2001
From: Peter Hutterer <[EMAIL
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 'evd
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 status
From: Peter Hutterer <[EMAIL PROTECTED]>
This removes all the meta-information about device properties (pending,
fromClient, range, valid_values, immutable).
---
Xi/extinit.c | 58 +--
Xi/xiproperty.c| 282
Xi/xiprop
From: Peter Hutterer <[EMAIL PROTECTED]>
If a property handler now bails out, return the error code to the caller. This
allows to be slightly more specific with the errors.
---
Xi/xiproperty.c| 63 +--
dix/devices.c |7 ++---
i
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 |
On Mon, Sep 22, 2008 at 11:30:59AM +0200, Simon Thum wrote:
>> -DeviceSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop)
>> +DeviceSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop,
>> + BOOL delete)
>> {
>> if (property == XIGetKnownProp
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 Mon, Sep 22, 2008 at 08:08:37PM +0200, Lukas Hejtmanek wrote:
> the current git head of the Xserver segfaults on any keystroke. Trace is
> attached:
Can I have a log please?
Cheers,
Peter
___
xorg mailing list
xorg@lists.freedesktop.org
http://list
ve to bump inputproto for new properties (e.g. ptr accel
configuration, a "driver" property, etc.)
Cheers,
Peter
>From 826b6441fe27304a37c0452457ff6c7ba952bfff Mon Sep 17 00:00:00 2001
From: Peter Hutterer <[EMAIL PROTECTED]>
Date: Tue, 23 Sep 2008 16:55:04 +0930
Subject: [
On Tue, Sep 23, 2008 at 08:36:13PM +0200, Sascha Hlusiak wrote:
> > Note that if you're using core clients, this is "intended" behaviour.
> > Remember that the ClientPointer (CP) always assigns a "primary" master
> > device to a core client.
> >
> > So the call order is something like:
> > Client r
On Wed, Sep 24, 2008 at 02:12:48AM +0300, Daniel Stone wrote:
> Maybe I'm missing something, but can we not do as SwitchCoreKeyboard
> used to do, and have all requests for keymap/whatever act on the device
> that last sent a key event to that client?
right, we could. The equivalent now would be S
On Tue, Sep 23, 2008 at 04:31:26PM -0700, Dan Nicholson wrote:
> I thought someone (you or keithp?) was going to just put xkbcomp into
> the server. Did anything ever happen with that? Just curious.
The usual lack of time issue. If you find the time to do it - go for it.
__
deletable flag.
If deletable is FALSE, the prop can only be deleted by the server/a driver,
and even then only if all handlers agree.
>From aa3b6cf0bd533bc264f3acddf14222a6e04f9d44 Mon Sep 17 00:00:00 2001
From: Peter Hutterer <[EMAIL PROTECTED]>
Date: Wed, 24 Sep 2008 10:18:14 +093
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
On Thu, Sep 25, 2008 at 03:19:51PM +0200, Søren Hauberg wrote:
> [...] now I guess I'll have to write an X driver that'll handle the
> touchscreen. The kernel module I'm targeting is using evdev, so that's the
> API I'll be working against.
> So, my question is: should I attempt to extend the X1
ConfigureProperty doesn't exist anymore, ChangeProperty has two parameters
less. SetProperty handler must return Status.
Mark all properties as non-deletable.
---
src/jstk_properties.c | 103 -
1 files changed, 34 insertions(+), 69 deletions(-)
dif
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 button
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 Sun, Sep 28, 2008 at 07:26:06PM +0200, Simon Thum wrote:
>> The screen coords are used to move the cursor and the scaling is done based
>> on
>> the axis ranges. Hence the different acceleration when you change the axis
>> range to 0,-1 (in which case the screen coords are used as axis ranges).
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 acc
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 (th
On Mon, Sep 29, 2008 at 03:08:00PM +0200, Søren Hauberg wrote:
> > Look at EvdevInitProperties(). Touchscreen-specifics should be only
> > available on
> > touchscreens, of course.
>
> This stuff seems to only be in git. It's not in any releases, right?
Yes, it's only in git. The property API was
e?
If not, xorg-.pc or just.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-propert
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)
> {
>win
On Mon, Sep 29, 2008 at 11:01:43PM +0100, [EMAIL PROTECTED] wrote:
> @@ -221,19 +220,21 @@ winMouseWheel (ScreenPtr pScreen, int iD
> void
> winMouseButtonsSendEvent (int iEventType, int iButton)
> {
> - xEvent xCurrentEvent;
> + EventList *events = InitEventList(GetMaximumEventsNu
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
>
On Tue, Sep 30, 2008 at 11:53:44AM +0200, Søren Hauberg wrote:
> Okay, so I'm attaching my latest patch. This should handle everything
> except setting/getting calibration parameters. I'll look into this
> after lunch today. I'd love some feedback on the patch, as I think
> this is the best structu
On Tue, Sep 30, 2008 at 03:14:17PM +0200, Søren Hauberg wrote:
> My impression is that the ones in EvdevRec means something different.
> The ones in the 'touchscreen' struct are the calibration parameters.
> 'min_x' is the smallest x value that the hardware actually sends, and
> similar for the oth
ne in
configure.ac and all drivers that matter already get the sdkdir anyway.
>From 95a970ed66184aff5b89434e00ca8c012c54d377 Mon Sep 17 00:00:00 2001
From: Peter Hutterer <[EMAIL PROTECTED]>
Date: Fri, 26 Sep 2008 10:42:05 +0930
Subject: [PATCH] Install xorg-evdev.pc for clients w
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 i
On Tue, Sep 30, 2008 at 04:56:57PM +0200, Søren Hauberg wrote:
> Okay, here's my latest attempt at a patch. I've renamed "flip_[x|y]"
> to "invert_[x|y]" and moved them into "EvdevRec", I've removed
> "swap_xy", and I've moved the reading of parameters to PreInit.
>
> I hope that's what you wanted
On Wed, Oct 01, 2008 at 12:21:06AM +0200, Simon Thum wrote:
> typedef struct _AbsoluteClassRec {
> /* Calibration. */
> int min_x;
> int max_x;
> int min_y;
> int max_y;
> int flip_x;
> int flip_y;
> int r
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 whites
Fix for Launchpad bug 276887: the X server still receives events even even
when VT-switched away. These events are then partially replayed on the
currently focused client when re-entering the VT.
Thanks to bryce and mjg59 for their help fixing this.
Peter Hutterer (2):
Close fd on
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 a
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 ha
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
On Thu, Oct 02, 2008 at 07:35:10AM -0700, Yan Seiner wrote:
> >> Xlib: extension "Generic Event Extension" missing on display ":0.0".
> (Unless I don't know enough to know better. Should I be concerned about
> this?)
No, and I've been meaning to silence this warning anyway.
Cheers,
Peter
Thanks, applied and pushed.
I added a man-page fix to this patch as well so the removal is documented.
Cheers,
Peter
On Thu, Oct 02, 2008 at 03:00:39PM +0100, Magnus Kessler wrote:
> I would like to propose to remove the repeater functionality completely from
> the synaptics touchpad driver.
On Fri, Oct 03, 2008 at 02:55:00AM +0200, [EMAIL PROTECTED] wrote:
> On Tue, Sep 23, 2008 at 01:52:53PM +0930, Peter Hutterer wrote:
> > driver kbd: hardcodes Ctrl + Alt + Backspace. (IMHO that's a bug anyway)
> > driver evdev: the XKB map decides what happens.
>
> I
On Tue, Oct 07, 2008 at 01:46:21AM -0300, Tiago Vignatti wrote:
> A problem that I see is in GetPointerEvents() function. It's bloated and
> confusing. It generates X events and also updates the cursor on screen.
> We don't need to mix this two actions in one function. For instance, I
> did a qu
On Tue, Oct 07, 2008 at 11:26:50AM +0200, Søren Hauberg wrote:
> 2008/10/1 Peter Hutterer <[EMAIL PROTECTED]>:
> > Ok, I took your patches, split them up and fiddled with them a bit.
>
> [snip]
>
> > 0005-Allow-specification-of-Min-Max-for-x-y-overriding-t.patch
&
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 han
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
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 the
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 inversio
On Wed, Oct 08, 2008 at 11:05:07PM +0200, Simon Thum wrote:
> > Not necessarily. Once the server has support for X, we can just remove it
> > from
> > the driver and say that you need at least server Y with this driver version.
> > Or, once the server has a "XYZ" property, you can just make e.g. "
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 gener
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 has 2 symbols^M
> > Ignoring extra symbols^M
> Errors from xkbcomp are not fatal to the X server^M
You
Apologies for not spotting this earlier.
On Mon, Sep 08, 2008 at 08:51:56AM -0700, Aaron Plattner wrote:
> commit 079625570d51e41569b73b2fd9237eb8f967f408
> Author: Aaron Plattner <[EMAIL PROTECTED]>
> Date: Mon Sep 8 08:50:52 2008 -0700
>
> Bump ABI major versions for the TryClientExceptio
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 11:50:40PM +0100, Magnus Kessler wrote:
> This series of patches removes support for the ancient XInput ABI 0.x from
> the synaptics driver, which in turn makes some more cleanup patches
> possible. There seems to be a consensus that supporting XInput ABI older
> than 2.x
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
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 order
Usually, the console is set to RAW in the kbd driver. If we hotplug all input
devices (i.e. the evdev driver for keyboards), the console is left as-is.
As a result, the evdev driver must put an EVIOCGRAB on the device to avoid
characters leaking onto the console. This again breaks many things, amon
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
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.
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 a/hw/xfree86/common/xf86Xinp
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 t
On Fri, Oct 17, 2008 at 02:42:31AM +0200, Tobias Jakobi wrote:
>type="string">true
You don't need this option, it's the default anyway.
>type="string">Buttons 5 4
this option isn't parsed by evdev, so it doesn't have any effect.
> I have some settings in the /etc/hal/fdi/policy/
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/x
IT ioctl usage on big endian 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 wit
ACK - untested though.
On Thu, Oct 16, 2008 at 01:10:01PM +0100, [EMAIL PROTECTED] wrote:
> ---
> xserver/hw/xwin/InitInput.c | 16 +---
> xserver/hw/xwin/win.h |2 ++
> xserver/hw/xwin/winmultiwindowwndproc.c |4 ++--
> xserver/hw/xwin/winwndpr
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 wi
ACK, untested.
On Thu, Oct 16, 2008 at 01:10:00PM +0100, [EMAIL PROTECTED] wrote:
> ---
> xserver/hw/xwin/wincursor.c | 33 -
> 1 file changed, 24 insertions(+), 9 deletions(-)
>
> Index: xorg-git/xserver/hw/xwin/wincursor.c
> ==
ACK, untested.
On Thu, Oct 16, 2008 at 01:10:02PM +0100, [EMAIL PROTECTED] wrote:
> ---
> xserver/hw/xwin/InitInput.c |3 +--
> xserver/hw/xwin/winkeybd.c | 20
> xserver/hw/xwin/winmouse.c | 25 +++--
> 3 files changed, 28 insertions(+), 20 dele
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
On Fri, Oct 17, 2008 at 08:45:09PM +0200, Tobias Jakobi wrote:
> > this option isn't parsed by evdev, so it doesn't have any effect.
> Hmm, are there currently any ways to configure evdev devices?
> The manpages seems a bit outdated. The is nearly nothing there that has
> to do with button mapping
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 H
1 - 100 of 1186 matches
Mail list logo
