DMXGetScreenCount(3)
π DMXGetScreenCount(3) π
okay bestie so this is a page from the Library Functions Manual and it's all about DMXGetScreenCount β the lil function that tells you how many back-end screens your Xdmx(1) server is out here controlling. it's giving census taker energy fr fr π³οΈβ¨
β¨ NAME β¨
DMXGetScreenCount β determine number of back-end screens π₯οΈπ₯οΈπ₯οΈ
πΈ SYNOPSIS πΈ
#include <X11/extensions/dmxext.h>
Bool DMXGetScreenCount(Display *dpy,
int *screen_count);
π¦ DESCRIPTION π¦
so like, DMXGetScreenCount() returns the number of back-end screens that a Xdmx(1) server controls. that's it, that's the whole vibe π
now here's the tea: since a DMX screen usually fills all of the available area on a back-end server, there's usually a one-to-one correspondence between DMX screens and backend servers. cute, simple, iconic. π
BUT β and this is the plot twist π«’ β it is also possible for a DMX screen to cover only part of the available area on a back-end server, and for more than one DMX screens to occupy different parts of the visible area on the same back-end server. so like, multiple DMX screens can lowkey share one back-end server's space. no cap.
also a DMX screen may be managed as a regular X screen in the Xdmx(1) server, or it may be joined with other DMX screens using Xinerama. main character energy either way. π
β RETURN VALUE β
DMXGetScreenCount() sets screen_count and returns True β unless there's a protocol error. so basically: True = slay, protocol error = not slay. π
π NOTES π
if Xinerama is active, only one logical screen will be available to clients of the Xdmx(1) server. yes, only one. don't panic, bestie π
however β and this is the important part β this call will accurately reflect the number of composite back-end screens that the Xdmx(1) server is using. so even when the clients only see one screen, this function is still out here telling you the real count. honest queen. π
π SEE ALSO π
and that's the whole page bestie, go forth and count your screens π«Άβ¨ this was X Version 11, libdmx 1.1.5, and it's giving DMXGetScreenCount(3) in the best way possible. mwah ππ
π¦ where this page comes from
- epel 10: libdmx-devel 1.1.5-5.el10_1 Β· MIT
- fedora 43: libdmx-devel 1.1.5-6.fc43 Β· MIT
- fedora 43: libdmx-devel 1.1.5-6.fc43 Β· MIT
- fedora 44: libdmx-devel 1.1.5-7.fc44 Β· MIT
- fedora 44: libdmx-devel 1.1.5-7.fc44 Β· MIT
- nixos 26.05: libdmx 1.1.5
- nixpkgs unstable: libdmx 1.1.5
- opensuse-leap 16.0: libdmx-devel 1.1.5-160000.3.2 Β· MIT
- opensuse-leap 16.0: libdmx-devel 1.1.5-160000.3.2 Β· MIT
- opensuse-leap 16.0: libdmx-devel 1.1.5-160000.3.2 Β· MIT
- opensuse-leap 16.0: libdmx-devel 1.1.5-160000.3.2 Β· MIT
- Copyright 2004 Red Hat Inc., Durham, North Carolina
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms