1. 18 Jan, 2013 2 commits
  2. 17 Jan, 2013 2 commits
  3. 14 Jan, 2013 1 commit
  4. 10 Jan, 2013 1 commit
  5. 09 Jan, 2013 1 commit
  6. 08 Jan, 2013 1 commit
  7. 07 Jan, 2013 1 commit
  8. 31 Dec, 2012 2 commits
  9. 30 Dec, 2012 1 commit
  10. 21 Dec, 2012 1 commit
  11. 19 Dec, 2012 1 commit
  12. 18 Dec, 2012 2 commits
  13. 15 Dec, 2012 3 commits
  14. 14 Dec, 2012 4 commits
  15. 13 Dec, 2012 1 commit
  16. 12 Dec, 2012 8 commits
  17. 11 Dec, 2012 1 commit
  18. 09 Dec, 2012 1 commit
    • Michael Natterer's avatar
      app: avoid inadvertent calls to image actions on file -> revert · b3486788
      Michael Natterer authored
      When reverting, we load a new image into the old image's existing
      displays, and replace all references to the old image by the new image
      in all GimpContext instances. We used to first update the displays and
      then the contexts, which would shortly produce an inconsistent state
      where the contexts were out of sync. When updating the displays with
      the new image, we sometimes call menu update functions which would
      then use that old image from the context when they should use the new
      one, and thus triggered callbacks as if the user had activated a menu
      (like image -> precision). To fix this, update the contexts before the
      displays. It is also more logical to first update model objects and
      then view objects.
      b3486788
  19. 08 Dec, 2012 3 commits
  20. 06 Dec, 2012 1 commit
  21. 05 Dec, 2012 1 commit
  22. 04 Dec, 2012 1 commit