Hello all,
I have installed *xoo* application on my machine which is
having MPX configured on it. I want to use this MPX on xoo display instead
of my original X server.So I checked the preferences in xoo and found
following two components
1) display
2) X server path (which was initi
On Tue, Feb 09, 2010 at 10:50:40AM +0100, Bradley T. Hughes wrote:
> On 02/09/2010 06:34 AM, ext Peter Hutterer wrote:
> >The really hard problem IMO is that given two touch points at coordinates
> >x1/y1 and x2/y2 and two different clients at these coordinates do we
> >- send the second touchpoint
Keith,
Please pull from my repo. Julien's and Dan's patches have dropped under the
table somehow, they were included in an earlier pull request. Benjamin's
change adds a set of new axis labels for multitouch to the list.
Cheers,
Peter
The following changes since commit db687f718f760ba254ab5199
Tags may be a list of comma-separated strings that match against a MatchTag
InputClass section. If any of the tags specified for a device match against
the MatchTag of the section, this match is evaluated true and passed on to
the next match condition.
Tags are specified as "input.tags" (hal) or "
Move tokenize out of the parser, make it a dix util function instead.
Splitting a string into multiple substrings is useful by other places, so
let's use it across the line. Future users include config/hal, config/udev
and of course the parser.
Example usage:
char **substrings = xstrtokenize(my_st
From: Dan Nicholson
Signed-off-by: Dan Nicholson
Reviewed-by: Peter Hutterer
---
hw/xfree86/common/xf86Xinput.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/xfree86/common/xf86Xinput.c b/hw/xfree86/common/xf86Xinput.c
index 8ac9d26..4604710 100644
--- a/hw/xfree
From: Dan Nicholson
In order to keep the number of InputClass sections manageable, allow
matches to contain multiple arguments. The arguments will be separated
by the '|' character. This allows a policy to apply to multiple types of
devices. For example:
Section "InputClass"
Identifi
From: Dan Nicholson
Sometimes it is desirable to skip adding specific input devices to the
server. The "Ignore" option is used similarly to Monitor sections so
that matched devices will not be added. BadIDChoice is returned to the
config backend so that it will clean up all resources.
Signed-off
From: Dan Nicholson
The config parser expects to find a newline at the end of each line, so
files ending without one would confuse it. A newline is inserted at the
end of the buffer in these situations. Additionally, switching to the
next config file is moved to the higher level to allow parsing
From: Dan Nicholson
Drivers and options specified in InputClass sections work on a "first
match wins" strategy. Let's be consistent when documenting it.
Signed-off-by: Dan Nicholson
Reviewed-by: Peter Hutterer
---
hw/xfree86/common/xf86Xinput.c |6 +++---
hw/xfree86/doc/man/xorg.con
This patchset contains a number of fixes for the new input configuration
interface and
three new features:
- the option to ignore certain devices.
- the option to match against multiple values
- the option to match devices against arbitrary tags
The patch to ignore devices was sent to the list
There doesn't seem to be anything that defines it and given that the
counterpart (the X internal malloc) was removed in
01cfba75229f4b9bf1e4fe80814931acdacde14c it's unlikely to work anyway.
Signed-off-by: Peter Hutterer
---
os/utils.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
On Fri, Feb 5, 2010 at 11:27:35 +1000, Peter Hutterer wrote:
> The only DDX currently using hotplugging is the xfree86 one and it looks
> like it'll stay that way for a bit. Move the initialization to the DDX,
> since Xephyr, Xnest, and friends don't need HAL or udev notifications.
>
> There's n
Adam Jackson writes:
> Signed-off-by: Adam Jackson
> ---
> hw/xfree86/common/xf86AutoConfig.c |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/hw/xfree86/common/xf86AutoConfig.c
> b/hw/xfree86/common/xf86AutoConfig.c
> index 1c4595e..384c7e5 100644
> --- a/hw/xfre
Executed from the ConfigureWindow request, right before sending
ConfigureNotify to the clients.
This commit breaks the ScreenRec ABI.
Signed-off-by: Francisco Jerez
---
v5: No need to bump the module ABI again.
dix/window.c |4
include/scrnintstr.h | 10 ++
2 files c
On 02/09/2010 06:34 AM, ext Peter Hutterer wrote:
> The really hard problem IMO is that given two touch points at coordinates
> x1/y1 and x2/y2 and two different clients at these coordinates do we
> - send the second touchpoint to the client that received the first
>touchpoint?
Another option
On Mon, Feb 08, 2010 at 10:25:12AM -0800, Francisco Jerez wrote:
> Executed from the ConfigureWindow request, right before sending
> ConfigureNotify to the clients.
>
> This commit breaks the ScreenRec ABI.
>
> Signed-off-by: Francisco Jerez
> ---
> dix/window.c |4
>
17 matches
Mail list logo
