summaryrefslogtreecommitdiffstats
path: root/waftools/features.py
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2014-08-16 21:43:13 +0200
committerwm4 <wm4@nowhere>2014-08-16 21:56:22 +0200
commitfe782a6e957c1f2d472a91eceef01ca5fd6f5cb7 (patch)
tree2007e80bdf53da8aab97be0bd4e0479fbd202695 /waftools/features.py
parent925c431ff7f68a7ea8b1fc0cd260edcf8b88fdc1 (diff)
downloadmpv-fe782a6e957c1f2d472a91eceef01ca5fd6f5cb7.tar.bz2
mpv-fe782a6e957c1f2d472a91eceef01ca5fd6f5cb7.tar.xz
x11: use xrandr to retrieve display refresh rate
Drop use of the ancient XF86VM, and use the slightly less ancient Xrandr extension to retrieve the refresh rate. Xrandr has the advantage that it supports multiple monitors (at least the modern version of it). For now, we don't attempt any dynamic reconfiguration. We don't request and listen to Xrandr events, and we don't notify the VO code of changes in the refresh rate. (The later works by assuming that X coordinates map directly to Xrandr coordinates, which probably is wrong with compositing window manager, at least if these use complicated transformations. But I know of no API to handle this.) It would be nice to drop use of the Xinerama extension too, but unfortunately, at least one EWMH feature uses Xinerama screen numbers, and I don't know how that maps to Xrandr outputs.
Diffstat (limited to 'waftools/features.py')
0 files changed, 0 insertions, 0 deletions