How to observe changes in connected monitors via Xlib?
Asked Answered
M

2

5

I'm trying to write a program that would detect external monitors being plugged in and automatically enable and configure them through Xlib. I know that there is XRandr extension that allows this. My question is, how do I enable receiving XRandr events to my application? What event mask should I use? I know that xev app is able to do this.

Magnificat answered 1/5, 2012 at 15:46 Comment(2)
Have you looked in the source of xev?Nomenclature
Here's what man 3 Xrandr says: A XRRScreenChangeNotifyEvent is sent to a client that has requested notification whenever the screen configuration is changed. A client can perform this request by calling XRRSelectInput, passing the display, the root window, and the RRScreenChangeNotifyMask mask.Nomenclature
R
5

Xev's source code:

Or:

  • git clone git://anongit.freedesktop.org/xorg/app/xev
Radiculitis answered 4/5, 2012 at 12:45 Comment(0)
H
4

For the second part, I issue the configuration directly to nvidia-settings.

I've cobbled together the first part from parts that I was able to find so that my HTPC system which is hooked to a TV that is horribly overscanned can reset the screen environment when the TV is turned on.

I'd be interested to see the pure C port of my efforts...

#!/usr/bin/python2

"""
Send RESET_COMMAND via os.system() call when xbc.randr reports
that a small screen (main monitor) has just changed configuration.
ie The secondary (TV) monitor has just been turned on.
"""

# Could also be xrandr settings, if need be #
# These values came from the nvidia-settings GUI with Base Mosaic enable with custom scaling on HDMI-0 determined experiementally
RESET_COMMAND = 'nvidia-settings --assign CurrentMetaMode="GPU-08c5ca05-d3cc-b022-4fab-3acab0500b7c.VGA-0: 1280x1024 +0+0, GPU-08c5ca05-d3cc-b022-4fab-3acab0500b7c.HDMI-0: 1920x1080 +1280+0 {viewportin=1920x1080, viewportout=1774x998+73+41}"'

MAIN_MONITOR_HEIGHT = 1024
MAIN_MONITOR_WIDTH = 1280

import os
# Do one reset at startup (login) - this may be a shortcoming of LXDM that has things wrong after the first login #
os.system(RESET_COMMAND)

import xcb
from xcb.xproto import *

import xcb.randr as RandR
from xcb.randr import NotifyMask, ScreenChangeNotifyEvent


def startup():
    """Hook up XCB_RANDR_NOTIFY_MASK_SCREEN_CHANGE"""
    # In the xcb.randr module, the result of
    # key = xcb.ExtensionKey('RANDR')
    # xcb._add_ext(key, randrExtension, _events, _errors)
    # is stored in xcb.randr.key and retrieved in some very odd manner =>
    randr = conn(RandR.key)
    randr.SelectInput(root.root, NotifyMask.ScreenChange)
    # may as well flush()
    conn.flush()



def run():
    """Listen for XCB_RANDR_SCREEN_CHANGE_NOTIFY"""
    currentTimestamp = 0
    connected = False
    startup()

    while True:
        try:
            event = conn.wait_for_event()
            connected = True
        except xcb.ProtocolException, error:
            print "Protocol error %s received!" % error.__class__.__name__
            break
        except Exception, error:
            print "Unexpected error received: %s" % error.message
            break

        # Once the ScreenChangeNotify Event arrives, filter down to the one we care about. #
        if isinstance(event, ScreenChangeNotifyEvent):
            # 3 consecutive events arrive with the same timestamp, #
            if currentTimestamp != event.config_timestamp:
                # so mask off the next two and #
                currentTimestamp = event.config_timestamp
                # mask off the disconnect altogether by looking at the initial screen size. #
                if ((event.width == MAIN_MONITOR_WIDTH) and (event.height == MAIN_MONITOR_HEIGHT)):
                    os.system(RESET_COMMAND)

    # won't really get here, will we?
    if connected:
        conn.disconnect()



conn = xcb.connect()
setup = conn.get_setup()
# setup.roots holds a list of screens (just one in our case) #
root = setup.roots[0]

run()
Handiwork answered 1/2, 2014 at 13:2 Comment(1)
Thanks a lot for this. Here is a C implementation of your program.Dickman

© 2022 - 2024 — McMap. All rights reserved.