summaryrefslogtreecommitdiff
path: root/git-gui/generate-script.sh
diff options
context:
space:
mode:
authorMark Levedahl <mlevedahl@gmail.com>2025-09-27 08:19:08 -0400
committerMark Levedahl <mlevedahl@gmail.com>2025-09-29 20:53:29 -0400
commit7754656a4c8fb5c04a7304b73348ce54e1c189fa (patch)
treeaa83ffbedda84d7e7d8ffeefe6631f37d09db203 /git-gui/generate-script.sh
parent8ccb2d4a762a0ea39c7f1df0712efbab3b7a4883 (diff)
gitk: do not invoke tk_setPalette
gitk uses themed widgets with a user selected theme, but also invokes tk_setPalette to configure colors for the non-themed widgets including the menubar. However, themes in general are expected to configure those colors already. The builtin themes (default, alt, clam, classic on unix/X11) all have compatible colors, and need no such reconfiguration, and (most, if not all) available themes set the options database for this purpose as well. Furthermore, gitk in the past avoided invoking tk_setPalette on Windows to avoid some issues. So, let's stop calling tk_setPalette everywhere, and just rely upon the selected theme (possibly user installed) to have set all needed colors. Note: if a user installs more than one theme using $themeloader, the last one installed will have defined the colors to be used. Those colors will probably be incorrect for any other set, including Tk's builtin set. Signed-off-by: Mark Levedahl <mlevedahl@gmail.com>
Diffstat (limited to 'git-gui/generate-script.sh')
0 files changed, 0 insertions, 0 deletions