itkvars(n)

💖 NAME 💖

itkvars — the variables that [incr Tk] uses, bestie. that's it, that's the whole vibe 🎀

---

✨ DESCRIPTION ✨

okay so listen 🫶 [incr Tk] just... creates some global variables for you, all by itself, automatically, like a little gremlin that also happens to be a great roommate. it manages them. you don't have to do anything. slay. 👑

⚠️ real talk though: unless the notes below say otherwise, application-specific code and users should treat these variables as read-only. like, look but don't touch, no cap. 🙈

• itk::library — the moment an interpreter gets created, [incr Tk] sets this variable up to hold the name of a directory, and that directory is the home of the system library of [incr Tk] scripts. 🏠✨

the initial value of itk::library comes from the ITK_LIBRARY environment variable if that thing exists — and if it doesn't, it falls back to a compiled-in value instead. that's the whole sourcing situation, fr fr. 🌸

so when [incr Tk] gets added to an interpreter, it runs the script "init.itk" in this directory. 💅 and that script? it goes looking for other script files named "init.xxx". mega-widget libraries will be automatically initialized if they install a script named "init.xxx" in this directory — where "xxx" is literally the name of the mega-widget library. iykyk. 🦋

example time, because examples ate: the [incr Widgets] library installs the script "init.iwidgets" in this directory. 🍓 and that script establishes the "iwidgets" namespace, and sets up autoloading for every single [incr Widgets] command. iconic behavior honestly 🌈⭐

---

🏷️ KEYWORDS 🏷️

itcl, itk, variables — the search-term trio, the main character energy of index entries 👑

---

anyway that's the page!! 💜 this one's from itk version 3.0, and it's the itkvars(n) manual page, dated the same era. mwah, go forth and read your variables responsibly 🎀✨💖