al_set_new_display_flags(3alleg5)

💖 NAME 💖

al_set_new_display_flags — a Allegro 5 API function, straight out of the 3alleg5 manual section. It's the little gremlin that decides what vibe every new display on your thread is gonna have ✨

---

📜 SYNOPSIS 📜

#include <allegro5/allegro.h>

void al_set_new_display_flags(int flags)

---

🦋 DESCRIPTION 🦋

Okay so bestie, here's the tea ☕: this function sets all the flags that get used when you create new displays on the calling thread. The flags argument is a bitfield — meaning you smoosh together any reasonable combination of the following constants with | and let it cook. 🍓

Here's the full roster, no skips, no cuts, we're doing all of them 👑

• ALLEGRO_WINDOWED — you're saying "prefer a windowed mode, pls". 🪟 Heads up though: under multi-head X (and not XRandR/TwinView), using more than one adapter is literally impossible because of bugs in X and GLX. al_create_display(3alleg5) will fail if more than one adapter is attempted to be used. 💀
• ALLEGRO_FULLSCREEN_WINDOW — makes the window span the entire screen 🌈. Unlike ALLEGRO_FULLSCREEN, this one will never attempt to modify the screen resolution, periodt. Instead, the pixel dimensions of the created display will be exactly the same as the desktop. The width and height you pass in are only used if the window is later switched out of fullscreen mode — initially they get ignored entirely, sorry babe 🙈.

Under Windows and X11, a fullscreen display created with this flag behaves differently from one created with the ALLEGRO_FULLSCREEN flag — even if the ALLEGRO_FULLSCREEN display is handed the desktop dimensions. The exact difference is platform dependent, but the things that may differ include: how alt-tab works, how fast you can toggle between fullscreen/windowed mode, and how additional monitors behave while your display is in fullscreen mode. It's giving "mystery meat" and the mystery is your OS 🫠.

Also, under X, using more than one adapter in multi-head mode or with true Xinerama enabled is impossible because of bugs in X/GLX — creation will fail if more than one adapter is attempted to be used.

• ALLEGRO_FULLSCREEN — you're saying "prefer a fullscreen mode". Under X, using more than one FULLSCREEN display when using multi-head X or true Xinerama is not possible because of bugs in X and GLX — display creation will fail if more than one adapter is attempted to be used. 😭

Note: Prefer using ALLEGRO_FULLSCREEN_WINDOW — it typically provides a better user experience because the monitor doesn't change resolution, and switching away from your game via Alt-Tab works smoothly. ALLEGRO_FULLSCREEN is typically less well supported compared to ALLEGRO_FULLSCREEN_WINDOW. Like, genuinely, bestie, choose the other one 💅

• ALLEGRO_RESIZABLE — the display is resizable (only applicable if combined with ALLEGRO_WINDOWED). Stretch that thing 🪄
• ALLEGRO_MAXIMIZED — the display window will be maximized (only applicable if combined with ALLEGRO_RESIZABLE). Since: 5.1.12
• ALLEGRO_OPENGL — requires the driver to provide an initialized OpenGL context after returning successfully. No context, no deal 🎀
• ALLEGRO_OPENGL_3_0 — requires the driver to provide an initialized OpenGL context compatible with OpenGL version 3.0. ⭐
• ALLEGRO_OPENGL_FORWARD_COMPATIBLE — if this flag is set, the OpenGL context created with ALLEGRO_OPENGL_3_0 will be forward compatible only, meaning all of the OpenGL API declared deprecated in OpenGL 3.0 will not be supported. Currently, a display created with this flag will not be compatible with Allegro drawing routines — the display option ALLEGRO_COMPATIBLE_DISPLAY will be set to false. So yeah, drawing stuff just won't work. Plan accordingly 🙏
• ALLEGRO_OPENGL_ES_PROFILE — used together with ALLEGRO_OPENGL, requests that the OpenGL context uses the OpenGL ES profile. A specific version can be requested with al_set_new_display_option(3alleg5). Note: Currently this is only supported by the X11/GLX driver. Since: 5.1.13
• ALLEGRO_OPENGL_CORE_PROFILE — used together with ALLEGRO_OPENGL, requests that the OpenGL context uses the OpenGL Core profile. A specific version can be requested with al_set_new_display_option(3alleg5). Note: Currently this is only supported by the X11/GLX driver. Since: 5.2.7
• ALLEGRO_DIRECT3D — requires the driver to do rendering with Direct3D and provide a Direct3D device. 🎮
• ALLEGRO_PROGRAMMABLE_PIPELINE — requires a programmable graphics pipeline. This flag is required to use ALLEGRO_SHADER(3alleg5) objects. Since: 5.1.6
• ALLEGRO_FRAMELESS — tries to create a window without a frame (i.e. no border or titlebar). This usually does nothing for fullscreen modes, and even in windowed modes it depends on the underlying platform whether it's supported or not. Fingers crossed 🤞 Since: 5.0.7, 5.1.2
• ALLEGRO_NOFRAME — the original name for ALLEGRO_FRAMELESS. This works with older versions of Allegro. Vintage era, we respect it 🧚
• ALLEGRO_GENERATE_EXPOSE_EVENTS — lets the display generate expose events.
• ALLEGRO_GTK_TOPLEVEL — creates a GTK toplevel window for the display, on X. This flag is conditionally defined by the native dialog addon. You must call al_init_native_dialog_addon(3alleg5) for it to succeed. ALLEGRO_GTK_TOPLEVEL is incompatible with ALLEGRO_FULLSCREEN. Since: 5.1.5
• ALLEGRO_DRAG_AND_DROP — if a display is created with the ALLEGRO_DRAG_AND_DROP flag, it will generate ALLEGRO_EVENT_DROP events when files or text are dropped over the display. 🗂️✨

[Unstable API]: This is an experimental feature and currently only works for the X11 backend.

Since: 5.2.9

And finally: 0 can be used for default values. Zero, the humble icon, ate 🫶

---

👀 SEE ALSO 👀

• al_set_new_display_option(3alleg5)
• al_get_display_option(3alleg5)
• al_set_display_option(3alleg5)

---

And that's the whole page, bestie 💜 This was al_set_new_display_flags(3alleg5), from the Allegro reference manual — go set some flags, you've got this 👑🌸