Git with broken hash generation to generate collisions between object IDs. Don't use this! https://undefinedbehavior.de/posts/commit-vandalism/

halilsen 465f03869a gitk: include y coord in recorded sash position ... 6cd80496e9 ("gitk: Resize panes correctly when reducing window size", 2020-10-03) introduces a mechanism to record previously-set sash positions to make sure that correct values are used while computing resize proportions. However, if we are not using ttk, then sash represents only the x coordinate and the recorded sash (`oldsash`) only includes the x coordinate. When we need to access the y coordinate via the recorded sash position, we generate the following Application Error popup: Error: expected integer but got "" expected integer but got "" expected integer but got "" while executing "$win sash place 0 $sash0 [lindex $s0 1]" (procedure "resizeclistpanes" line 38) invoked from within "resizeclistpanes .tf.histframe.pwclist 2818" (command bound to event) To fix this, if we are not using ttk, we append the sash positions with the y coordinates before recording them to match the use_ttk case. Signed-off-by: Halil Sen <halil.sen@gmail.com> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>		2022-05-11 18:04:33 +10:00
po	gitk: rename zh_CN.po to zh_cn.po	2019-09-17 14:58:12 -07:00
.gitignore	gitk: Ignore gitk-wish buildproduct	2013-01-30 21:12:16 +11:00
gitk	gitk: include y coord in recorded sash position	2022-05-11 18:04:33 +10:00
Makefile	gitk: Makefile: create install bin directory	2016-12-12 11:01:12 +11:00