1. 23 May, 2014 1 commit
  2. 21 May, 2014 2 commits
  3. 16 May, 2014 1 commit
  4. 06 May, 2014 1 commit
  5. 04 May, 2014 1 commit
  6. 02 May, 2014 1 commit
    • Michael Natterer's avatar
      app: make things behave more reasonable with multiple monitors · 843866e7
      Michael Natterer authored
      There is now a preference option that determines whether windows
      should be opened on the same monitor as before. It should be disabled
      when the machine gets monitors plugged/unplugged dynamically ("laptop")
      and enabled when there is a static multi-monitor setup ("wokstation").
      This is merely the current simplistic policy on top of the newly added
      underlying infrastructure:
      - pass integer monitor numbers around in all places where we already
        pass around a GdkScreen. Pass the "current" monitor to these changed
        APIs, where "current" is either the monitor where the action-triggering
        widget is, or if that is unavailable the monitor where the mouse is.
      - add gimp_widget_get_monitor() in order to easily get to the monitor,
        just like gtk_widget_get_screen().
      - add screen and monitor parameters in some places that were missed
      - in sessionrc, save all window positions relative to the window's
        monitor, and save the monitor separately, if it's not the screen's
        primary monitor.
      - when restoring window positions, use the stored monitor when the new
        prefs options says so (use the screen's primary monitor if there is
        no stored monitor), otherwise use current monitor that is now passed
  7. 18 Apr, 2014 1 commit
  8. 04 Apr, 2014 1 commit
    • Michael Natterer's avatar
      app: commit ongoing tool operations on tool change instead of cancelling · 88e4d7e4
      Michael Natterer authored
      On tool change, we used to simply halt tools before switching to the
      new one, which meant losing ongoing live-previewed tool changes, like
      transforms, warps and color corrections. This change makes them being
      applied to the image instead before switching to the new tool:
      Add enum value GIMP_TOOL_ACTION_COMMIT that is passed to
      GimpTool::control() before tool switching. Handle the new enum value
      in all tools, and actually commit the previewed stuff. This changes
      the behavior of GimpCageTool, GimpImageMapTool, GimpTransformTool and
  9. 07 Jun, 2013 4 commits
  10. 31 May, 2013 1 commit
  11. 30 May, 2013 2 commits
  12. 25 May, 2013 1 commit
  13. 17 May, 2013 2 commits
  14. 13 May, 2013 1 commit
  15. 28 Apr, 2013 1 commit
  16. 25 Apr, 2013 2 commits
  17. 21 Apr, 2013 1 commit
  18. 16 Apr, 2013 4 commits
  19. 12 Apr, 2013 1 commit
  20. 09 Mar, 2013 1 commit
  21. 12 Nov, 2012 1 commit
  22. 06 Sep, 2012 1 commit
    • Michael Natterer's avatar
      Bug 683462 - cropping with rectangular select tool leaves misaligned... · e546f2b4
      Michael Natterer authored
      Reset the tool on image changes again, but not if only the active
      drawable changes, so keep bug #678890 closed:
      Introduce new dirty flag GIMP_DIRTY_ACTIVE_DRAWABLE and set it on all
      tools' dirty_mask except for rect select. Check the new flag when
      reseting the active tool because of a drawable change.
  23. 26 Jul, 2012 1 commit
    • Michael Natterer's avatar
      Bug 678890 - Selection box handles do not respond after changing layer · 078128bb
      Michael Natterer authored
      Make sure that temporarily setting/unsetting tool->control's "preserve
      tool across image changes" does not mess up the default value:
      Introduce gimp_tool_control_push/pop_preserve() which restores the old
      state automatically, and use it in all tools, instead of saying
      set_preserve(TRUE/FALSE) around image changes.
  24. 05 May, 2012 1 commit
    • Michael Natterer's avatar
      app: don't call gimp_image_flush() when cancelling GimpImageMapTool · e7e8c9ef
      Michael Natterer authored
      because the tool might be cancelled from some other place opening an
      undo group, so flushing the image would update menus and whatnot while
      that other operation is running, with unforeseeable side
      effects. Also, flusing the image here is not needed because we didn't
      change anything in the image. Instead, make sure manually that the
      display is updated correctly after restoring GimpImageMapTool's
      temporary editing.
  25. 02 May, 2012 6 commits