1. 23 May, 2017 1 commit
    • Ell's avatar
      enums: run gimp-mkenums from the build dir · 5bcde32c
      Ell authored
      Commit 1e6acbd4 modified the
      generated enum recipes to run gimp-mkenums from the source
      directory, instead of the build directory, so that only the
      basenames of the corresponding header files would appear in
      the comment at the top of the generated files.  This was a
      mistake -- $(GIMP_MKENUMS) is expecting to be invoked from the
      build directory.
      Switch back to running gimp-mkenums from the build directory.  To
      avoid including the relative path from the build directory to the
      source directory in the generated file, add a @basename@ production
      variable to gimp-mkenums, which exapnds to the basename of the
      input file, and use it instead of @filename@ in the recipes for the
      generated enum files.
  2. 22 May, 2017 1 commit
    • Ell's avatar
      enums: don't write generated enum files to src-dir if unchanged · f9fa0d1b
      Ell authored
      When regenerating an enum file, don't copy it back to the source
      directory if it hasn't actually changed.  This allows using a read-
      only source directory where the enum header is newer than the
      generated file, as long as they're not really out of sync.
      OTOH, *do* touch the generated source-dir file even when unchanged,
      in order to avoid re-running its recipe on the next build, however,
      allow this to silently fail (which is harmless).
  3. 19 May, 2017 1 commit
  4. 16 May, 2017 1 commit
  5. 06 May, 2017 1 commit
    • Ell's avatar
      enums: generate enum files in source dir · 1e6acbd4
      Ell authored
      We check them into git, so this makes it easier to keep them in
      sync when using a separate build directory.
      Case in point -- this commit also syncs a few enum files that went
      out-of-sync with their headers.
  6. 09 Feb, 2017 1 commit
    • Michael Natterer's avatar
      libgimpconfig: gimp_config_reset_properties(): reset only changed properties · 7111eadf
      Michael Natterer authored
      This avoids a lot of useless notifications when resetting an object,
      and fixes e.g. the "reset tool options" behavior of GimpTransformTool,
      which did completely reset itself instead of just behaving like all
      non-default options had changed.
      And probably breaks some things that were relying on these redundant
  7. 08 Jan, 2017 1 commit
  8. 06 Jan, 2017 1 commit
  9. 18 Oct, 2016 1 commit
  10. 17 Oct, 2016 1 commit
  11. 12 Oct, 2016 1 commit
  12. 02 Oct, 2016 1 commit
  13. 30 Sep, 2016 2 commits
  14. 28 Sep, 2016 2 commits
  15. 13 Sep, 2016 1 commit
  16. 04 Sep, 2016 1 commit
  17. 31 Aug, 2016 1 commit
  18. 25 Jun, 2016 1 commit
    • Richard Kreckel's avatar
      Bug 768044 - Fix many typos · dd9b0fc5
      Richard Kreckel authored
      This fixes many typos in comments and one in a user-visible string (msgid
      "center abscisse" changed to "center abscissa" in affected po files. too).
  19. 08 Jun, 2016 1 commit
  20. 07 Jun, 2016 2 commits
  21. 06 Jun, 2016 1 commit
  22. 05 Jun, 2016 3 commits
  23. 25 May, 2016 1 commit
  24. 16 May, 2016 1 commit
  25. 09 May, 2016 1 commit
  26. 08 May, 2016 1 commit
  27. 16 Apr, 2016 2 commits
  28. 26 Mar, 2016 1 commit
  29. 09 Feb, 2016 1 commit
    • Michael Natterer's avatar
      libgimpconfig: add a new set of macros to register serialitable properties · a3f127bf
      Michael Natterer authored
      The old GIMP_CONFIG_INSTALL_PROP_FOO() have the problem of always
      passing NULL as the GParamSpec's "nick". I have no clue what we were
      thinking back then, but this has always been a major design flaw
      because (among other problems) it makes it impossible to fully
      auto-generate GUIs based on properties.
      Added GIMP_CONFIG_PROP_FOO() macros which do have a "nick" parameter,
      will deprecate the old macros as soon as everything is ported.
  30. 14 Dec, 2015 1 commit
  31. 20 Aug, 2015 1 commit
    • Michael Natterer's avatar
      Bug 555562 - GIMP should ask before applying working space profile · 77dac3ea
      Michael Natterer authored
      Get rid of the "configurable RGB working space profile".
      Instead, turn GimpColorConfig's "rgb-profile" property into a
      "Preferred RGB profile" thing that is only a hint and never used
      without explicit user interaction. Present it next to the built-in
      profile in the profile combo boxes and call it "Preferred" in the
      prefs dialog and its tooltip.
      Most importantly, don't use it as the image's profile when the image
      is not tagged with a profile. Untagged images are now always in the
      sRGB or linear RGB built-in color spaces.
      This commit reduces the "Apply color profile" dialog on file import to
      a simple "Convert to built-in RGB", but that dialog is about to be
      moved to the core and improved anyway.
  32. 10 Jul, 2015 1 commit
    • Michael Natterer's avatar
      libgimpcolor, *: change GimpColorProfile to be a GObject · c102dde9
      Michael Natterer authored
      it used to be a typedef to gpointer and actually was a cmsHPROFILE.
      Change its API to be more "standard", remove the public close()
      function. The object caches both the cmsHPROFILE and the data/length
      ICC blob, so conversions between the two become obsolete (simply call
      get_lcms_profile() or get_icc_profile()).
      Adapt everything to the new API, but port it in a naive way for now,
      the code doesn't take advantage of the new possibilities yet (like
  33. 03 Jun, 2015 2 commits