tk_setPalette(n)

📦
version 9.0.3 · 4 versions
, in alpine 3.23, alpine 3.24, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable

🎀 tk_setPalette, tk_bisque — modify the Tk color palette 🎀

okay bestie, welcome to a Tk Built-In Commands manual page — this one is all about tk_setPalette and tk_bisque, and it is lowkey iconic 💅✨

✨ NAME ✨

tk_setPalette, tk_bisque — modify the Tk color palette 🎨

🌸 SYNOPSIS 🌸

tk_setPalette background
tk_setPalette name value ?name value ...?
tk_bisque

💖 DESCRIPTION 💖

The tk_setPalette procedure changes the color scheme for Tk. It does this by modifying the colors of existing widgets and by changing the option database so that future widgets will use the new color scheme. It's giving whole-app glow-up, no cap 🌈.

If tk_setPalette is invoked with a single argument, the argument is the name of a color to use as the normal background color; tk_setPalette will compute a complete color palette from this background color. One background color in, entire palette out — main character energy fr fr 💅.

Alternatively, the arguments to tk_setPalette may consist of any number of name-value pairs, where the first argument of the pair is the name of an option in the Tk option database and the second argument is the new value to use for that option. The following database names are currently supported:

  • activeBackground
  • activeForeground
  • background
  • disabledForeground
  • foreground
  • highlightBackground
  • highlightColor
  • insertBackground
  • selectBackground
  • selectColor
  • selectForeground
  • troughColor

tk_setPalette tries to compute reasonable defaults for any options that you do not specify. You can specify options other than the above ones and Tk will change those options on widgets as well. This feature may be useful if you are using custom widgets with additional color options. Custom widget color side quest? Obsessed 🦋.

Once it has computed the new value to use for each of the color options, tk_setPalette scans the widget hierarchy to modify the options of all existing widgets. For each widget, it checks to see if any of the above options is defined for the widget. If so, and if the option's current value is the default, then the value is changed; if the option has a value other than the default, tk_setPalette will not change it. The default for an option is the one provided by the widget ([lindex [$w configure $option] 3]) unless tk_setPalette has been run previously, in which case it is the value specified in the previous invocation of tk_setPalette. Respecting the defaults? We love to see it 😌✨.

After modifying all the widgets in the application, tk_setPalette adds options to the option database to change the defaults for widgets created in the future. The new options are added at priority widgetDefault, so they will be overridden by options from the .Xdefaults file or options specified on the command-line that creates a widget. It's setting the vibe, but not being a control freak about it 💖.

The procedure tk_bisque is provided for backward compatibility: it restores the application's colors to the light brown (“bisque”) color scheme used in Tk 3.6 and earlier versions. Vintage Tk color moment, we bow 🍓👑.

🔥 KEYWORDS 🔥

  • bisque
  • color
  • palette

okay that's the whole manual page, bestie 🫶 this is tk_setPalette(n) from Tk 4.0 — footer source/version energy is Tk 4.0, page tk_setPalette(n), and the date isn't printed in the footer text I have, so no fake date from me, just pure manual-page sparkle 💖✨

📦 where this page comes from