1. 07 Aug, 2020 3 commits
  2. 06 Aug, 2020 2 commits
    • Piotr Drąg's avatar
      Update Polish translation · 30d73c63
      Piotr Drąg authored
      30d73c63
    • Jehan's avatar
      gitlab-ci: rename the CI jobs. · bd6abe06
      Jehan authored
      The Linux CI job names are too long and are not recognizable on the web
      GUI unless you hover the widgets with the mouse to read tooltips. Remove
      the "/testing" part (if people want to know exactly which Debian we use
      for our builds, they can always look at the script) and move left the
      differenciating parts (i.e. autotools/meson/clang/distcheck) so that
      these are visible in a glance, even when ellipsing long job names.
      bd6abe06
  3. 05 Aug, 2020 5 commits
    • Anders Jonsson's avatar
      Update Swedish translation · b8d15136
      Anders Jonsson authored
      b8d15136
    • Jehan's avatar
      libgimpwidgets: improve/fix more of GimpMemSizeEntry. · d886bb1b
      Jehan authored
      Looking further at this widget, many things are not right. Here are the
      changes:
      - Use binary prefixes (i.e. kibibyte, mebibyte and gibibyte) instead of
        decimal ones. We are making binary shifts so we were actually showing
        the wrong units.
      - Round the value to the closest integer when showing it, not towards 0.
        Otherwise I had cases where it was showing 7GiB for an actual value of
        7.69GiB (default as computed by GIMP from my actual physical memory).
        Note that I am actually unsure even rounding makes sense. Shouldn't we
        rather show double values with a few digits after the decimal points?
        For such values, I think it would make sense.
      - Do not edit the internally saved accurate value when the entry is
        edited to the same less accurate value as our saved value would be
        shown too. In particular when changing the display unit to a bigger
        one, we don't want to lose accuracy. This is especially true for low
        values. Say you don't have a lot of memory and you set the Tile cache
        size to 1.5GiB (1536MiB), you certainly don't want it to become either
        1 or 2GiB when switching display unit to GiB. Now even if the number
        will still display with less accuracy, the internal value will stay
        accurate.
      d886bb1b
    • Jehan's avatar
      libgimpwidgets: fix setting GimpMemSizeEntry value with unit change. · 0be4e5c1
      Jehan authored
      This bug doesn't happen when setting value through the GUI as in such
      case, the unit never changed. It happened when setting a value which
      could not be properly displayed by current unit (typically smaller than
      1 in this unit, or with remainder).
      In such a case, we should not manually set private->shift before
      gimp_int_combo_box_set_active(), or the callback was failing to
      reconfigure the GtkAdjustement, in particular min and max values.
      
      As a consequence, hitting a Preferences reset, with a GimpMemSizeEntry
      in Gigabytes, it got reset to Kilobytes with the max values capped at
      4096. So I realized a Reset ended me with a Tile cache size of 4096 KB
      in particular, which is of course ridiculously small and would be a
      problem if one doesn't notice the issue immediately.
      0be4e5c1
    • Marco Ciampa's avatar
      Updated Italian translation · b8d96c49
      Marco Ciampa authored
      b8d96c49
    • Dimitris Spingos's avatar
      Updated Greek translation · a68989e7
      Dimitris Spingos authored
      a68989e7
  4. 04 Aug, 2020 1 commit
  5. 03 Aug, 2020 4 commits
  6. 02 Aug, 2020 9 commits
  7. 01 Aug, 2020 15 commits
  8. 31 Jul, 2020 1 commit