summaryrefslogtreecommitdiff
path: root/fixesproto.txt
AgeCommit message (Collapse)Author
2023-06-01Allow client to force server to terminate if it exitsDemi Marie Obenour
This is intended to be used by screen lockers, where the server must exit if the screen locker does, to avoid a security hole. As suggested by Alan Coopersmith, this is implemented using a new flag for the disconnect mode of the XFixes extension. Includes wording suggestions from Peter Hutterer. Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
2021-04-29xfixes: Add ClientDisconnectModeOlivier Fourdan
The Xserver itself is capable of terminating itself once all X11 clients are gone, yet in a typical full session, there are a number of X11 clients running continuously (e.g. the Xsettings daemon, IBus, etc.). Those always-running clients will prevent the Xserver from terminating, because the actual number of X11 clients will never drop to 0. To solve this issue directly at the Xserver level, this add new entries to the XFixes extension to let the X11 clients themselves specify the disconnect mode they expect. Typically, those X11 daemon clients would specify the disconnect mode XFixesClientDisconnectFlagTerminate to let the Xserver know that they should not be accounted for when checking the remaining clients prior to terminate. Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
2020-08-08Fix spelling/wording issuesAlan Coopersmith
Found by using: codespell --builtin clear,rare,usage,informal,code,names Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
2015-09-22cursor-name is after cursor-image in GetCursorImageAndNamePeter Harris
Signed-off-by: Peter Harris <pharris@opentext.com>
2015-04-08HideCursor/ShowCursor: Fix the interpretation of the window argumentOwen W. Taylor
In the implementation of HideCursor/ShowCursor in the xserver code, the window passed in only identifies a screen, not a portion of the window tree, and it's been that way since the beginning. Changing the implementation at this point would likely break existing code, and the main usage of this protocol (magnifiers) only needs the global behavior, so change the protocol to document the actual behavior. Reviewed-by: Keith Packard <keithp@keithp.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
2013-02-11CreatePointerBarrier takes a window, not a drawablePeter Hutterer
Technically this is a change in the protocol, but we've never supported anything but a Window. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2011-02-09fixesproto v5: Pointer barriersAdam Jackson
v3: Review fixes: - INT16 not CARD16 for coordinates - BadDevice not BadMatch Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Adam Jackson <ajax@redhat.com>
2009-08-03Document behaviour of CursorNotifies with XI2 servers.Peter Hutterer
CursorNotifies are only sent for the ClientPointer to avoid confusion in the client. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2009-08-03Hide/ShowCursor works on all master pointers in XI2.Peter Hutterer
Servers supporting XI2 will hide all cursors when a client requests HideCursor. This is arguably closest to the original intent of the request - to not display a cursor above the given window. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2008-09-22ChangeSaveSet with map=Unmap means 'unmap', not 'don't remap'Keith Packard
The semantics in the spec were conflicting, and the implementation did the 'don't remap' version which was not useful. The server implementation has been fixed, this change clarifies the specification to match that design.
2007-01-09Typo fixes in XFixes protocol specAlan Coopersmith
2007-01-09Update XFixes protocol spec to match XFixes 4.0Alan Coopersmith
Add ExpandRegion, HideCursor & ShowCursor requests Correct description of version numbering to match XFixes conventions
2007-01-09Move fixes protocol description to the new canonical location/name.Eric Anholt