image_surface_resolve(3)

📦
version 0.7.1 · 2 versions
, in nixos 26.05

💅 image_surface_resolve(3) — the Arcan Lua API, but make it make sense

okay bestie, so you're digging around in image_surface_resolve(3) from the Arcan Lua API — here's the whole vibe, no cap 🫶

✨ NAME ✨

image_surface_resolve — pulls the current image properties, but in world-space 🌍✨

🎀 SYNOPSIS 🎀

proptbl
image_surface_resolve( vid )

🦋 DESCRIPTION 🦋

so here's the tea ☕ — most of the surface_ class of functions hand you their results in object space. kinda local, kinda self-centered, main character energy honestly.

image_surface_resolve is the one that actually goes out and does the socializing 🚶‍♀️💨 — it traverses the related set of object hierarchies and resolves the world-space ones that will be used when compositing the output. that's the whole job. iconic.

🌸 NOTES 🌸

  1. the fields chillin' inside proptbl are, in this exact order: (x, y, z, width, height, depth, angle, roll, pitch, yaw, opacity and order) 📋✨
  2. okay so this one's cost is highly variable 😭 — because the rendering pipeline normallys caches both the resolved properties and the resulting transformation matrices, if possible. so like... sometimes it's fast, sometimes it's doing the whole walk. vibe check accordingly.
lowkey heads up: "highly variable cost" is not a drill, bestie — don't call this in a hot loop and then act surprised 💀

🧚 EXAMPLE 🧚

function image_surface_resolve0()
      a = fill_surface(32, 32, 255, 0, 0);
      b = fill_surface(64, 64, 0, 255, 0);
      link_image(b, a);
      move_image(a, 100, 100);
      move_image(b, 50, 50);
      props = image_surface_resolve(b);
      print(string.format("%d %d", props.x, props.y));
end

like, that's it. that's the whole slay 🔥

💜 SEE ALSO 💜

go read those too, iykyk 👑

image · October 2026 · that's the page, that's the version, that's the date — mwah 💋✨ bye bestie, go resolve some surfaces 🦋💖

📦 where this page comes from