itkvars(3itk)

✨ itkvars — the [incr Tk] lore drop ✨

okay bestie, this is itkvars(3itk) from the [incr Tk] manual, and it's literally just the tea on the global variables [incr Tk] keeps for you 🫶

---

🌸 NAME 🌸

itkvars — the variables that [incr Tk] uses, no cap 💅

---

🎀 DESCRIPTION 🎀

So here's the vibe: [incr Tk] creates and manages a lil set of global variables all by itself, automatically, no input from you needed 👑

⚠️ heads up bestie — unless it says otherwise down below, you should treat these variables as read-only. That goes for your application-specific code and for users. Don't be out here writing to them, okay? 🙈

💖 itk::library

When an interpreter gets created, [incr Tk] sets this variable up to hold the name of a directory — specifically the one containing the system library of [incr Tk] scripts 📁✨

The starting value of itk::library comes from the ITK_LIBRARY environment variable if that one exists, and if it doesn't, it comes from a compiled-in value instead. Either way, you're covered 🧚

When [incr Tk] is added to an interpreter, it runs the script "init.itk" in this directory. And that script goes looking for other script files named "init.xxx" 👀

Mega-widget libraries get initialized automatically if they drop a script named "init.xxx" into this directory, where "xxx" is the name of the mega-widget library. it's giving plug-and-play, honestly 🌈

For example: the [incr Widgets] library installs the script "init.iwidgets" in this directory. That script establishes the "iwidgets" namespace, and it sets up autoloading for every [incr Widgets] command. iconic behaviour, truly 👑

---

🔥 KEYWORDS 🔥

• itcl
• itk
• variables

---

and that's the whole page, bestie — short, sweet, slay 💅

sign-off szn: this one's from the itk crew, version 3.0, and yeah it's filed under itkvars(3itk). go forth and don't touch the read-only variables, mwah 💖✨