1. 15 3月, 2015 1 次提交
    • M
      gitk: Only write changed configuration variables · 995f792b
      Max Kirillov 提交于
      When gitk contains some changed parameter, and there is an existing
      instance of gitk where the parameter is still old, it is reverted to
      that old value when that instance exits.
      
      Instead, store a parameter in config only if it has been modified in
      the exiting instance. Otherwise, preserve the value which currently is in
      file.  This allows editing the configuration when several instances are
      running, without rollback of the modification if some other
      instance where the configuration was not edited is closed last.
      
      For scalar variables, use trace(3tcl) to detect their change. Since
      `trace` can send bogus events, doublecheck if the value has really
      been changed, but once it is marked as changed, do not reset it back
      to unchanged ever, because if user has restored the original value,
      it's the decision which should be stored as well as modified value.
      
      Treat view list especially: instead of rewriting the whole list, merge
      individual views. Place old and updated views in their old places,
      add new ones to the end of list. Collect modified views explicitly, in
      newviewok{} and delview{}.
      
      Do not merge geometry values. They are almost always changing because
      user moves and resises windows, and there is no way to find which one of
      the geometries is most desired. Just overwrite them unconditionally,
      like earlier.
      Signed-off-by: NMax Kirillov <max@max630.net>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      995f792b
  2. 02 3月, 2015 2 次提交
  3. 30 10月, 2014 3 次提交
  4. 08 8月, 2014 2 次提交
  5. 27 6月, 2014 2 次提交
  6. 15 6月, 2014 6 次提交
  7. 21 2月, 2014 1 次提交
  8. 23 1月, 2014 1 次提交
  9. 22 1月, 2014 1 次提交
  10. 21 1月, 2014 5 次提交
  11. 14 12月, 2013 1 次提交
  12. 02 12月, 2013 5 次提交
  13. 31 10月, 2013 1 次提交
    • P
      gitk: Tag display improvements · 4399fe33
      Paul Mackerras 提交于
      When a commit has many tags, the tag icons in the graph display can
      easily become so wide as to push the commit message off the right-hand
      edge of the graph display pane.  This changes the display so that if
      there are more than 3 tags or they would take up more than a quarter
      of the width of the pane, we instead display a single tag icon with
      a legend inside it like "4 tags...".  If the user clicks on the tag
      icon, gitk then displays all the tags in the diff display pane.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      4399fe33
  14. 17 5月, 2013 1 次提交
  15. 13 5月, 2013 2 次提交
  16. 11 5月, 2013 4 次提交
  17. 01 4月, 2013 1 次提交
    • G
      gitk: Move hard-coded colors to .gitk · 252c52df
      Gauthier Östervall 提交于
      The Preferences dialog gives control of the colors of some elements of
      the gitk user interface, but many are hard-coded in the gitk script.
      In order to allow these to be customized through the gitk config
      file, these other colors are stored in variables which can be set
      in the config file, thus providing a way for color schemes to be stored
      and shared.
      
      For win32, this makes the default foreground color that of window text
      rather than button text.
      Signed-off-by: NGauthier Östervall <gauthier@ostervall.se>
      [paulus@samba.org: Reworded commit message to be clearer,
       changed filesepfgcolor to black]
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      252c52df
  18. 30 1月, 2013 1 次提交