Bug 5282 - "temporary" property for XRandR configuration changes
Summary: "temporary" property for XRandR configuration changes
Status: RESOLVED DUPLICATE of bug 14255
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/RandR (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high enhancement
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard: 2011BRB_Reviewed
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-08 15:27 UTC by Ben Anderson
Modified: 2018-06-13 16:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Ben Anderson 2005-12-08 15:27:42 UTC 
The XRandR spec should have an option to mark a change as "temporary". Such
changes would not generate XRRUpdateConfiguration events. This flag would be
used by fullscreen programs (e.g. games) to note that the intent is not to
change the desktop size, but to lower the hardware resolution for better
performance. Temporary changes would also revert after the client that made the
change disconnects.

Alternately, "temporary" changes could generate a different event
(XRRUpdateConfigTemp maybe?) so that clients could still listen for them in case
they're interested in every miniscule resolution change (screen savers/lockers
come to mind).
Comment 1 Ben Anderson 2005-12-08 15:31:51 UTC 
Misread the manpage. "XRRUpdateConfiguration" should be
"XRRScreenChangeNotifyEvent". Similarly, a better suggestion for the temporary
might be "XRRScreenTempChangeNotifyEvent"
Comment 2 Adam Jackson 2005-12-09 07:48:17 UTC 
better idea: XRRGrab() and XRRUngrab().  allow an argument to Grab to specify
whether sending RR events to other apps should be suppressed.
Comment 3 Daniel Stone 2007-02-27 01:29:18 UTC 
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 4 Adam Jackson 2018-06-13 16:45:31 UTC 

*** This bug has been marked as a duplicate of bug 14255 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.