RandR 1.2 output properties and options

Srecko Morovic smorovic at gmail.com
Sat Nov 18 05:07:29 PST 2006

Keith Packard <keithp <at> keithp.com> writes:
> This raises some interesting questions -- who gets to set the range of
> valid values? Can you set and query the pending value separately from
> the current value?

Besides a range set by X server based on driver, display and config file
information, there should be a method to block certain property (or mode switch)
change and ability to have limited alowed "subset" of settings, as a policy. I
think this control ability(API) should be given to window managers as they are
responsible for a lot more (input interception, even compositing).

What this could allow is better fail-safe way to tackle misbehaving apps which
are constantly trying to set strange property/mode ( similar concept is
applicable also to those that steal input, focus or trying to stay on top). WM
could be configured to catch on certain input combination and after reverting to
default mode and at the same point disallowing property or mode changes, it can
launch session control application, which can for example present user with
tasklist and ability to kill bad process (similar to ctrl+alt+del event in 


More information about the xorg mailing list