DMXAddInput(3)

💖 DMXAddInput — bestie, let's attach a new input 💖

okay so this is a libdmx page, and the whole vibe is: you've got an Xdmx(1) server and you wanna bolt a new input onto it (or re-bolt one you took off earlier). These three functions do exactly that. No cap.

---

✨ NAME ✨

DMXAddInput, DMXAddBackendInput, DMXAddConsoleInput — attach a new input 🫶

---

🌸 SYNOPSIS 🌸

#include <X11/extensions/dmxext.h>

Bool DMXAddInput(Display *dpy,
                 unsigned int mask,
                 DMXInputAttributes *attr,
                 int *id);
Bool DMXAddBackendInput(Display *dpy,
                        int screen,
                        int sendsCore,
                        int *newId);
Bool DMXAddConsoleInput(Display *dpy,
                        const char *name,
                        int sendsCore,
                        int *newId);

---

🦋 DESCRIPTION 🦋

So DMXAddInput() is the main character here — it attaches a new input (or a previously detached input, we love a comeback arc ✨) to the Xdmx(1) server.

• mask tells you which fields inside attr are actually active (like, which ones we're paying attention to, bestie).
• id returns the device id of the first device in the series</... wait no — the device id of the first device in the series that gets added. 💅

The value of mask is computed from these values:

• DMXInputType
• DMXInputPhysicalScreen
• DMXInputSendsCore

And here's the DMXInputAttributes structure, in all its glory:

typedef struct {
    DMXInputEnum inputType;
    int          physicalScreen;
    int          physicalId;
    Bool         isCore;
    Bool         sendsCore;
    const char   *name;
    Bool         detached;
} DMXInputAttributes;

inputType can be either DMXConsoleInputType or DMXBackendInputType — pick your fighter. 🌈

• For console devices, name is the one that specifies the display to be used.
• For back-end devices, physicalScreen specifies the Xdmx(1) screen number.

If sendsCore is True, the new device gets added as a true core device. Iconic.

If a device was removed earlier with DMXRemoveInput(3), then an attempt will be made to reconnect the previous devices — and heads up, sendsCore is ignored in that case. 😭

---

🎀 the helper functions 🎀

DMXAddBackendInput() is a lil helper that's used to add input from a back-end server. With this one:

• screen refers to the back-end screen
• sendsCore is True if the new input should send core events (and it is ignored if the input has been detached)
• newId will hold the device id of the first device in the series added

DMXAddConsoleInput() is the other helper, used to add input from a console. With this one:

• name is the name of the console display
• sendsCore is True if the new input should send core events (and it is ignored if the input has been detached)
• newId will hold the device id of the first device in the series added

---

💅 RETURN VALUE 💅

DMXAddInput() returns True on success and False otherwise. That's it, that's the whole thing. ✨

DMXAddInput() can also generate these errors, and ngl you should know them:

• BadValue — if inputType is invalid or physicalScreen is out of range
• BadAccess — if the input has already been attached, or if the backend screen is currently detached

---

🙈 NOTES 🙈

• Local devices cannot be attached or detached. Just not a thing, bestie. 💀
• Attributes that are not specified will default to 0. This may lead to unintended results — so like, actually specify your stuff, fr fr.

🫶 lowkey important: that default-to-zero thing is not a vibe. Set your fields.

---

👑 SEE ALSO 👑

• DMXRemoveInput(3)
• DMX(3)
• Xdmx(1)

---

and that's the page!! 💖 this was libdmx version 1.1.5, part of X Version 11, and the whole thing is dated the same way that footer always is. stay slay, go attach ur inputs, mwah 🎀🦋🌸