checkbutton(n)

πŸ“¦
version 9.0.3 Β· 3 versions
, in alpine 3.23, alpine 3.24, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable

hey bestie πŸ’– welcome to checkbutton(n) from Tk Built-In Commands β€” this is the glow-up manual for making and driving 'checkbutton' boolean selection widgets, and we're gonna get you comfy with every last detail, no cap ✨

🌸 NAME 🌸

okay so checkbutton is literally the command to create and manipulate 'checkbutton' boolean selection widgets πŸŽ€ that's the whole assignment, and you're gonna slay it.

✨ SYNOPSIS ✨

checkbutton pathName ?options?

πŸ’… STANDARD OPTIONS πŸ’…

bestie, these are the standard options you can sprinkle on β€” every single one is here, so don't panic:

  • -activebackground
  • -disabledforeground
  • -padx
  • -activeforeground
  • -font
  • -pady
  • -anchor
  • -foreground
  • -relief
  • -background
  • -highlightbackground
  • -takefocus
  • -bitmap
  • -highlightcolor
  • -text
  • -borderwidth
  • -highlightthickness
  • -textvariable
  • -compound
  • -image
  • -underline
  • -cursor
  • -justify
  • -wraplength

See the options manual entry for details on the standard options β€” that's where the tea is πŸ«–

πŸŽ€ WIDGET-SPECIFIC OPTIONS πŸŽ€

-command

Command-Line Name: -command Β· Database Name: command Β· Database Class: Command

Specifies a Tcl command to associate with the button πŸ’– this command is typically invoked when mouse button 1 is released over the button window. the button's global variable (the -variable option) will be updated before the command is invoked β€” order matters, bestie, no cap.

-height

Command-Line Name: -height Β· Database Name: height Β· Database Class: Height

Specifies a desired height for the button. If an image or bitmap is being displayed in the button then the value is in screen units (i.e. any of the forms acceptable to Tk_GetPixels); for text it is in lines of text. If this option is not specified, the button's desired height is computed from the size of the image or bitmap or text being displayed in it. lowkey convenient.

-indicatoron

Command-Line Name: -indicatoron Β· Database Name: indicatorOn Β· Database Class: IndicatorOn

Specifies whether or not the indicator should be drawn. Must be a proper boolean value. If false, the -relief option is ignored and the widget's relief is always sunken if the widget is selected and raised otherwise. that's the rule, periodt.

-offrelief

Command-Line Name: -offrelief Β· Database Name: offRelief Β· Database Class: OffRelief

Specifies the relief for the checkbutton when the indicator is not drawn and the checkbutton is off. The default value is β€œraised”. By setting this option to β€œflat” and setting -indicatoron to false and -overrelief to β€œraised”, the effect is achieved of having a flat button that raises on mouse-over and which is depressed when activated. This is the behavior typically exhibited by the Bold, Italic, and Underline checkbuttons on the toolbar of a word-processor, for example. honestly iconic toolbar behavior.

-offvalue

Command-Line Name: -offvalue Β· Database Name: offValue Β· Database Class: Value

Specifies value to store in the button's associated variable whenever this button is deselected. Defaults to β€œ0”.

-onvalue

Command-Line Name: -onvalue Β· Database Name: onValue Β· Database Class: Value

Specifies value to store in the button's associated variable whenever this button is selected. Defaults to β€œ1”.

-overrelief

Command-Line Name: -overrelief Β· Database Name: overRelief Β· Database Class: OverRelief

Specifies an alternative relief for the checkbutton, to be used when the mouse cursor is over the widget. This option can be used to make toolbar buttons, by configuring -relief flat -overrelief raised. If the value of this option is the empty string, then no alternative relief is used when the mouse cursor is over the checkbutton. The empty string is the default value.

-selectcolor

Command-Line Name: -selectcolor Β· Database Name: selectColor Β· Database Class: Background

Specifies a background color to use when the button is selected. If indicatorOn is true then the color is used as the background for the indicator regardless of the select state. If indicatorOn is false, this color is used as the background for the entire widget, in place of background or activeBackground, whenever the widget is selected. If specified as an empty string then no special color is used for displaying when the widget is selected.

-selectimage

Command-Line Name: -selectimage Β· Database Name: selectImage Β· Database Class: SelectImage

Specifies an image to display (in place of the -image option) when the checkbutton is selected. This option is ignored unless the -image option has been specified. noted, bestie πŸ“

-state

Command-Line Name: -state Β· Database Name: state Β· Database Class: State

Specifies one of three states for the checkbutton: normal, active, or disabled. In normal state the checkbutton is displayed using the -foreground and -background options. The active state is typically used when the pointer is over the checkbutton. In active state the checkbutton is displayed using the -activeforeground and -activebackground options. Disabled state means that the checkbutton should be insensitive: the default bindings will refuse to activate the widget and will ignore mouse button presses. In this state the -disabledforeground and -background options determine how the checkbutton is displayed. so drama, so clear.

-tristateimage

Command-Line Name: -tristateimage Β· Database Name: tristateImage Β· Database Class: TristateImage

Specifies an image to display (in place of the -image option) when the checkbutton is in tri-state mode. This option is ignored unless the -image option has been specified.

-tristatevalue

Command-Line Name: -tristatevalue Β· Database Name: tristateValue Β· Database Class: Value

Specifies the value that causes the checkbutton to display the multi-value selection, also known as the tri-state mode. Defaults to β€œβ€.

-variable

Command-Line Name: -variable Β· Database Name: variable Β· Database Class: Variable

Specifies the name of a global variable to set to indicate whether or not this button is selected. Defaults to the name of the button within its parent (i.e. the last element of the button window's path name).

-width

Command-Line Name: -width Β· Database Name: width Β· Database Class: Width

Specifies a desired width for the button. If an image or bitmap is being displayed in the button then the value is in screen units (i.e. any of the forms acceptable to Tk_GetPixels); for text it is in characters. If this option is not specified, the button's desired width is computed from the size of the image or bitmap or text being displayed in it.

🌈 DESCRIPTION 🌈

okay so real talk: the checkbutton command creates a new window (given by the pathName argument) and makes it into a checkbutton widget. Additional options, described above, may be specified on the command line or in the option database to configure aspects of the checkbutton such as its colors, font, text, and initial relief. The checkbutton command returns its pathName argument. At the time this command is invoked, there must not exist a window named pathName, but pathName's parent must exist. that's not a suggestion, bestie β€” that's the vibe check πŸ’…

A checkbutton is a widget that displays a textual string, bitmap or image and a square called an indicator. If text is displayed, it must all be in a single font, but it can occupy multiple lines on the screen (if it contains newlines or if wrapping occurs because of the -wraplength option) and one of the characters may optionally be underlined using the -underline option. A checkbutton has all of the behavior of a simple button, including the following: it can display itself in either of three different ways, according to the -state option; it can be made to appear raised, sunken, or flat; it can be made to flash; and it invokes a Tcl command whenever mouse button 1 is clicked over the checkbutton. yes, it's giving full button behavior with a checkmark moment πŸŽ€

In addition, checkbuttons can be selected. If a checkbutton is selected then the indicator is normally drawn with a selected appearance, and a Tcl variable associated with the checkbutton is set to a particular value (normally 1). The indicator is drawn with a check mark inside. If the checkbutton is not selected, then the indicator is drawn with a deselected appearance, and the associated variable is set to a different value (typically 0). The indicator is drawn without a check mark inside. In the special case where the variable (if specified) has a value that matches the tristatevalue, the indicator is drawn with a tri-state appearance and is in the tri-state mode indicating mixed or multiple values. (This is used when the check box represents the state of multiple items.) The indicator is drawn in a platform dependent manner. Under Unix and Windows, the background interior of the box is β€œgrayed”. Under Mac, the indicator is drawn with a dash mark inside. platform-dependent indicator lore, fr fr πŸ¦‹

By default, the name of the variable associated with a checkbutton is the same as the name used to create the checkbutton. The variable name, and the β€œon”, β€œoff” and β€œtristate” values stored in it, may be modified with options on the command line or in the option database. Configuration options may also be used to modify the way the indicator is displayed (or whether it is displayed at all). By default a checkbutton is configured to select and deselect itself on alternate button clicks. In addition, each checkbutton monitors its associated variable and automatically selects and deselects itself when the variables value changes to and from the button's β€œon”, β€œoff” and β€œtristate” values. it's literally always watching its variable, bestie πŸ‘€βœ¨

πŸ’… WIDGET COMMAND πŸŽ€

okay so the checkbutton command makes a whole new Tcl command, and its name is literally pathName. bestie, that command is your remote control for the widget β€” you use it to poke at it and do stuff. it goes like this, every time:

pathName option ?arg ...?

so option and the args are what decide exactly what the command does. and here's the menu of commands you can pull on a checkbutton, no cap:

  • pathName cget option β€” returns the current value of whatever config option you name. option can be any of the values the checkbutton command accepts. it's giving "just checking what you're set to rn" πŸ’…
  • pathName configure ?option? ?value option value ...? β€” query or modify the widget's configuration options, the classic. if you give it no option, it hands you back a list describing every available option for pathName (peep Tk_ConfigureInfo for how that list is formatted, iykyk). if you give it option with no value, you get back a list describing just that one named option β€” and that list is literally identical to the matching sublist of the big no-option list. and if you pass one or more option-value pairs? then it modifies those widget option(s) to the value(s) you gave, and returns an empty string. option can be any value the checkbutton command accepts.
  • pathName deselect β€” deselects the checkbutton and sets the associated variable to its "off" value. bye bye selection πŸ¦‹
  • pathName flash β€” flashes the checkbutton! it does this by redisplaying the checkbutton several times, alternating between active and normal colors. and when the flash is done, the checkbutton is left in exactly the same normal/active state it was in when you called the command β€” no lingering chaos. ⭐ this command is ignored if the checkbutton's state is disabled.
  • pathName invoke β€” does exactly what would've happened if the user clicked it with the mouse: toggles the selection state of the button and invokes the Tcl command associated with the checkbutton, if there is one. the return value is the return value from that Tcl command, or an empty string if there's no command associated with the checkbutton. also ignored if the checkbutton's state is disabled. πŸ”₯
  • pathName select β€” selects the checkbutton and sets the associated variable to its "on" value. we love a committed queen πŸ‘‘
  • pathName toggle β€” toggles the selection state of the button, redisplays it, and modifies its associated variable to reflect the new state. flip flop flip flop πŸ™ˆ

⌨️ BINDINGS ⌨️

Tk automatically creates class bindings for checkbuttons, and they give them this default behavior:

  1. On Unix systems, a checkbutton activates whenever the mouse passes over it and deactivates whenever the mouse leaves the checkbutton. On Mac and Windows systems, when mouse button 1 is pressed over a checkbutton, the button activates whenever the mouse pointer is inside the button, and deactivates whenever the mouse pointer leaves the button. platform differences, classic 😭
  2. When mouse button 1 is pressed over a checkbutton, it is invoked β€” its selection state toggles and the command associated with the button is invoked, if there is one.
  3. When a checkbutton has the input focus, the space key causes the checkbutton to be invoked. Under Windows, there are additional key bindings; plus (+) and equal (=) select the button, and minus (-) deselects the button. multilingual keyboard slay πŸ’œ
🫢 big caveat bestie: if the checkbutton's state is disabled, then none of the above actions occur β€” the checkbutton is completely non-responsive. like, ghosted. πŸ’€

and you can change how checkbuttons behave by defining new bindings for individual widgets, or by redefining the class bindings. your widget, your rules ✨


🌸 EXAMPLE 🌸

this example shows a group of uncoupled checkbuttons. look at them, all independent and thriving:

labelframe .lbl -text "Steps:"
checkbutton .c1 -text Lights  -variable lights
checkbutton .c2 -text Cameras -variable cameras
checkbutton .c3 -text Action! -variable action
pack .c1 .c2 .c3 -in .lbl
pack .lbl

Lights, Cameras, Action! 🎬 not me being obsessed with this demo ngl


πŸ” SEE ALSO πŸ”

🏷️ KEYWORDS 🏷️

checkbutton, widget


okay that's the whole vibe, bestie β€” this was Tk 4.4, the checkbutton(n) page, and yeah the footer date situation is just that classic Tk 4.4 era energy. go forth and toggle responsibly πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from