al_set_new_bitmap_wrap(3)

πŸ“¦
version 5.2.11.3 Β· 2 versions
, in arch rolling

πŸŽ€ al_set_new_bitmap_wrap(3) πŸŽ€

This page is from the Library Functions Manual, bestie, and it’s the Allegro 5 API entry for al_set_new_bitmap_wrap. Buckle up, it’s short but lowkey important πŸ’…


πŸ’– NAME πŸ’–

al_set_new_bitmap_wrap β€” Allegro 5 API, periodt ✨

✨ SYNOPSIS ✨

#include <allegro5/allegro.h>

void al_set_new_bitmap_wrap(ALLEGRO_BITMAP_WRAP u, ALLEGRO_BITMAP_WRAP v)

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this function sets the texture wrapping settings for newly created bitmaps β€” and yes, that’s on the current thread, bestie 🧡✨

The signature takes u and v, both typed as ALLEGRO_BITMAP_WRAP, and that’s literally the whole vibe.

Typically you take advantage of this feature either via the primitives addon (see al_draw_prim(3) and others) or via custom shaders (see ALLEGRO_SHADER(3)). Obsessed with the flexibility, ngl πŸ’œ

Note: In the context of custom shaders, Direct3D and OpenGL have different granularities for controlling this setting. Direct3D sets wrapping setting for each sampler separately, while OpenGL sets it per-texture. This interacts particularly poorly with the primitives addon which (for backwards compatibility) alters the wrapping setting. To minimize this issue, use a wrapping setting that’s not ALLEGRO_BITMAP_WRAP_DEFAULT. 🚨 This one’s important, bestie β€” don’t sleep on it 😭

🌈 SINCE 🌈

5.2.8, yup πŸ’«

[Unstable API]: This is an experimental feature. πŸ§ͺ✨

🫢 SEE ALSO 🫢


Source/version: Allegro reference manual Β· page: al_set_new_bitmap_wrap(3) Β· date: not printed on this one, bestie πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from
  • arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms