SoCallbackList(3)

💖 SoCallbackList — a whole vibe ✨

okay bestie, so this is Coin's SoCallbackList(3), and it's literally the group chat of callback functions 💅 she's a container for callback function pointers, and honestly? she keeps it all together for you. no cap.

---

🌸 NAME 🌸

SoCallbackList — she's a container for callback function pointers. that's the whole job. and she ATE. 👑

---

🎀 SYNOPSIS 🎀

first things first, you gotta let her in the door:

#include <Inventor/lists/SoCallbackList.h>

✨ Public Member Functions ✨

this is the roster, the main characters, the whole friend group:

SoCallbackList (void)
~SoCallbackList ()
void addCallback (SoCallbackListCB *f, void *userData=NULL)
void removeCallback (SoCallbackListCB *f, void *userdata=NULL)
void clearCallbacks (void)
int getNumCallbacks (void) const
void invokeCallbacks (void *callbackdata)

look at that lineup. iconic behavior fr fr. 🫶

---

🦋 Detailed Description 🦋

okay so, real talk: SoCallbackList is a container for callback function pointers. that's her. that's the whole personality.

the way she works is, she stores callback function pointers — and she also holds onto the user-specified extra data you want passed to those callbacks, so you're not out here losing your stuff. and then she gives you a method for triggering all those callback functions. so it's store + stash + fire. lowkey elegant. ✨

---

💜 Constructor & Destructor Documentation 💜

🌷 SoCallbackList::SoCallbackList (void )

Default constructor. that's it, that's her origin story. she's born. 🎀

🌷 SoCallbackList::~SoCallbackList (void )

Destructor. she's saying goodbye. it's giving bittersweet. 😭

---

🔥 Member Function Documentation 🔥

⭐ void SoCallbackList::addCallback (SoCallbackListCB * f, void * userdata = NULL)

Append the callback function f to the list. she's joining the squad 💖 and when she gets invoked, she's gonna be handed userdata. so don't forget to bring it, bestie.

⭐ void SoCallbackList::removeCallback (SoCallbackListCB * f, void * userdata = NULL)

Remove callback f from the list. she's leaving the group chat. no drama, just logistics. 🙈

⭐ void SoCallbackList::clearCallbacks (void )

Remove all callbacks in the list. everybody out. the group chat is now empty. 💀

⭐ int SoCallbackList::getNumCallbacks (void ) const

Returns the number of callback functions. the headcount. the census. the "how many of us are in here" check. 🔢

⭐ void SoCallbackList::invokeCallbacks (void * callbackdata)

okay so THIS is the main event. she invokes all the callback functions, passing the userdata and the callbackdata as the first and second argument, respectively. so argument one is the userdata, argument two is the callbackdata. don't mix them up, i'm literally begging. 🫶

and here's the part you need to know, bestie:

All callbacks registered when the method is invoked will be triggered, even though if the code in one callback removes another callback.

read that again. she already decided who's coming to the party. if somebody dips mid-party, the party still includes them. that's just how she runs it. 💅

It is safe for a callback to remove itself or any other callbacks during execution. so you can absolutely do the dramatic self-exit. she's got you. no undefined behavior jumpscare here. 🌈

fr fr: triggering is snapshot-y. removals during execution are safe. that's the whole deal. don't overthink it. ✨

---

👑 Author 👑

Generated automatically by Doxygen for Coin from the source code. so technically a robot wrote her bio and we're all just living in it. 😭

---

and that's the page, bestie!! 🎀 this was Coin version 4.0.10, dated Thu Jun 25 2026 00:00:00, and the manual page is SoCallbackList(3). slay, go forth, and may all your callbacks fire in the right order. 💖✨🦋