Age | Commit message (Collapse) | Author | Files | Lines |
|
The DDX (xfree86 anyway) maintains its own device list in addition to the one
in the DIX. CloseDevice will only remove it from the DIX, not the DDX. If the
server then restarts (last client disconnects), the DDX devices are still
there, will be re-initialised, then the hal devices come in and are added too.
This repeats until we run out of device ids.
This also requires us to strdup() the default pointer/keyboard in
checkCoreInputDevices.
X.Org Bug 14418 <http://bugs.freedesktop.org/show_bug.cgi?id=14418>
(cherry picked from commit 6d22a9615a0e6ab3d00b0bcb22ff001b6ece02ae)
|
|
I can apply patches, really.
(cherry picked from commit 333e7123dc484888d79c0f5aa3977bd72f1eb341)
|
|
(cherry picked from commit e7a364425547103a98acabfc67d16e1ae0c2967f)
|
|
(cherry picked from commit 056a2ce02ce85013e89055ee44a7aa3eabedac09)
|
|
Fixes a bug where pointers were being invalidated after a realloc.
(cherry picked from commit 72f2197545e734cd0aa785d05a57b2fc0351a763)
|
|
|
|
Introduces dixLookupSelection() API.
Removes NumCurrentSelections from API.
|
|
Introduces dixLookupProperty() API.
|
|
Need to just fix the callers.
|
|
|
|
|
|
Otherwise XkbRemoveResourceClient may try to dereference it lateron.
X.Org Bug 12830 <http://bugs.freedesktop.org/show_bug.cgi?id=12830>
|
|
To recap: the original XC-SECURITY extension disallowed background "None" if
the window was untrusted. XACE 1.0 preserved this check as a hook function.
XACE pre-2.0 removed the hook and first abolished background "None entirely,
then restored it as a global on/off switch in response to Bug #13683.
Now it's back to being per-window, via a flag instead of a hook function.
|
|
|
|
NO, NO, NO.
NO.
The only way this could possibly be worse is if you were viewing it in
Comic Sans.
|
|
Opening a device is not really "reading" it.
Requests that globally configure a device should require "manage" access.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cross screen and clip the coordinates before updating the motion history
so that it will have the same contents as the events that are reported.
|
|
Relative events that generates both core and extention
events will have its axis cliped and screen changed by
miPointerSetPosition when the events are processed. For
absolute and non core-generating relative events the
axis must be clipped if we shouldn't end up completely
outside the defined ranges (if any).
|
|
Restore the rescaling code for x and y axis when generating
motion events.
|
|
Don't use a possitive value as a marker for if a max-value
is defined on the valuators. Use the existence of a valid
value range instead. This will also make it possible to
define arbitrary start and end-values for min and max as
long as min < max.
|
|
Send valuator information for all event types, not only for
MotionEvents and absolute button events.
|
|
|
|
|
|
|
|
Composite uses an unmap/map cycle to trigger backing pixmap allocation
and cliprect recomputation when a window is redirected or unredirected.
To avoid protocol visible side effects, map and unmap events are
disabled temporarily. However, when a window is unmapped it is also
removed from grabs and loses focus, but these state changes are not
disabled.
This change supresses the unmap side effects during the composite
unmap/map cycle and fixes this bug:
http://bugzilla.gnome.org/show_bug.cgi?id=488264
where compiz would cause gnome-screensaver to lose its grab when
compiz unredirects the fullscreen lock window.
|
|
(first_valuator + num_valuators) must never be larger than the number of axes,
otherwise DIX freaks out. And from looking at libXI, anything larger than 6 is
wrong too.
(cherry picked from commit 9f6ae61ad12cc2813d04405458e1ca5aed8a539e)
|
|
|
|
|
|
996b621bec1bbc4fb21970c75eaec62053bc6ccb deleted a couple lines too many
|
|
If a device is already initialised (i.e. the virtual core devices) during
IASD, don't init them again. This fixes a leak.
|
|
General code cleanup, whitespace, dead code removal, added missing prototypes.
Made Xquartz come to foreground later in startup, so it doesn't appear for Xquartz -version
(cherry picked from commit 36922e8ff4316c93843aa3fe959cf8df3c7d5892)
|
|
From the X11 protocol spec:
"If background None is specified, the window has no defined background."
This means that toolkits and apps cannot rely on the "transparent" nature
of the current implementation! At some point before the next release,
XACE will switch back to a solid background as the default.
|
|
Initialise num_events to 1, so we always send a proximity event, and then
optionally valuator events. Also make sure mieq can deal with valuator
events sent after proximity events.
|
|
Conflicts:
Xext/EVI.c
Xext/bigreq.c
Xext/cup.c
Xext/dpms.c
Xext/fontcache.c
Xext/mitmisc.c
Xext/xcmisc.c
Xext/xf86bigfont.c
Xext/xtest.c
configure.ac
dbe/dbe.c
hw/darwin/darwin.h
hw/darwin/darwinEvents.c
hw/darwin/iokit/xfIOKit.h
hw/darwin/iokit/xfIOKitCursor.c
hw/darwin/quartz/fullscreen/fullscreen.c
hw/darwin/quartz/fullscreen/quartzCursor.c
hw/darwin/quartz/quartz.c
hw/darwin/quartz/quartzCommon.h
hw/darwin/quartz/quartzCursor.c
hw/darwin/quartz/xpr/dri.c
hw/darwin/quartz/xpr/dristruct.h
hw/darwin/quartz/xpr/xprCursor.c
hw/darwin/quartz/xpr/xprFrame.c
hw/xfree86/modes/xf86RandR12.c
include/cursor.h
miext/rootless/rootlessCommon.h
miext/rootless/rootlessScreen.c
miext/rootless/rootlessWindow.c
render/picturestr.h
Trying to pick up the pieces from the darwin churn here...
|
|
|
|
|
|
|
|
|
|
|
|
ships with Xlib. This is considered temporary, until server-side XCB can
solve the problem programmatically.
|
|
Imported changes from xorg-server-1.2-apple to make master more current wrt
file layout, build system changes, and dead code removal.
|