1. 17 Jul, 2021 2 commits
  2. 13 Jul, 2021 2 commits
  3. 14 Jun, 2021 1 commit
  4. 09 Jun, 2021 1 commit
    • Agata Cacko's avatar
      Fix setting 'modified' state to readonly documents · 884a0641
      Agata Cacko authored
      Before this commit, the readonly documents would accept
      first setModified(true) call, but then ignore
      setModified(false) call because "it's read-only so it cannot
      be modified".
      That's because it was checking d->modified (current state)
      instead of mod (the desired state).
      That caused gamut masks (which are marked read-only) to ignore
      setModified(false) call and ask the user to save the document.
  5. 24 May, 2021 2 commits
  6. 13 May, 2021 1 commit
  7. 11 May, 2021 1 commit
  8. 03 Apr, 2021 1 commit
  9. 31 Mar, 2021 1 commit
    • Sachin Jindal's avatar
      Add Resize Options in Export · 2c58abc4
      Sachin Jindal authored and Dmitry Kazakov's avatar Dmitry Kazakov committed
      Move imagesize from plugins to libs/ui
      Introduce new parameter in Export hierarchy
      Creates a new Menu entry similar to Export.
      Reuse the Scale Image to New Size in Export.
      Bug: 397172
  10. 27 Mar, 2021 1 commit
  11. 10 Mar, 2021 2 commits
  12. 18 Feb, 2021 1 commit
    • Santhosh Anguluri's avatar
      Fix "Default colour model for new images" · d41048cc
      Santhosh Anguluri authored and Dmitry Kazakov's avatar Dmitry Kazakov committed
      Before this commit, only working color space is changed
      when default color model is changed. But that does not
      change anything to the new image dialog. This MR provides
      an option to use a default set color model or last used
      color model using a checkbox.
      Tested as follows:
      1)Config Krita -> Color Management -> General ->
          Change default color model for new images(with checkbox checked).
      2) Make a new image
      3) The new default model and bitdepth appears.
  13. 03 Feb, 2021 1 commit
    • Dmitry Kazakov's avatar
      Workaround recursive calls in UndoStack · 6fc84c8b
      Dmitry Kazakov authored
      In some cases, when the user clicks in the history docker too
      quickly, the undo requests may arrive recursively. Because there
      are a few commands that demand processEvent() calls after their
      execution. This patch workarounds the recursive issue using the
      ticket-like system for the requests and ensuring that all of them
      are executed at the topmost level of recursion.
  14. 12 Jan, 2021 1 commit
    • Dmitry Kazakov's avatar
      Fix modified state of the image after changing layer visibility · 0c53270b
      Dmitry Kazakov authored
      Now KisDocument has a special field imageModifiedWithoutUndo, which
      records the fact if modifying the image without undo, e.g. by changing
      layer visibility. This field ca be reset only by saving the image,
      not by changing the state if the undo stack.
  15. 15 Dec, 2020 1 commit
  16. 27 Nov, 2020 1 commit
  17. 10 Nov, 2020 1 commit
  18. 29 Oct, 2020 1 commit
    • Agata Cacko's avatar
      Generate pixelart previews using FastTransformation · ab3890d0
      Agata Cacko authored
      Before this commit, all previews for .kra files were generated
      using the Bicubic algorithm.
      This commit checks if there is a chance that the file is a pixel art
      file, and in such case creates a preview using the FastTransformation
      (presumably Nearest Neighbour, but it isn't said in the Qt
      documentation) algorithm.
      It is determined that it is safe to use FastTransformation algorithm
      in case when both of those conditions are true:
      - the file is smaller than the preview size
      - the exact scale in both dimensions is integer (so it will enlarge
      all pixels the same way).
  19. 15 Oct, 2020 1 commit
    • Agata Cacko's avatar
      Fix autosave with filenames beginning with numbers · 38eefbfd
      Agata Cacko authored
      Before this commit, a file called `1-file.kra` would autosave
      as `.-file.kra-autosave.kra`.
      This commit fixes that behaviour and now it will autosave
      as `.1-file.kra-autosave.kra`.
      More cases:
      - `1file.kra` would become `.file.kra-autosave.kra`
      - `1 file.kra` would become `. file.kra-autosave.kra`
      Now all of those work correctly and contain the beginning number.
  20. 09 Oct, 2020 1 commit
    • Halla Rempt's avatar
      Make the filter models instantiable · 54901206
      Halla Rempt authored
      The filter models (KisResourceModel, KisTagModel, KisTagResourceModel)
      are QSortFilterProxy models that wrap their respective KisAllResourcesModel,
      KisAllTagsModel, KisAllTagResourceModel model classes.
      The *All* models are singletons, unique per resource type. The wrapper
      models have per-model state, namely the active filters.
  21. 06 Oct, 2020 1 commit
  22. 01 Oct, 2020 1 commit
  23. 25 Sep, 2020 1 commit
  24. 21 Sep, 2020 1 commit
    • Sharaf Zaman's avatar
      Fix the way URIs are handled · 2a87a898
      Sharaf Zaman authored
      Prior to this commit, URIs were expected to resolve to
      some file on Android, but this assumption turned out to
      be flawed. URIs may or may not resolve. What is expected
      way of opening a file using them is to either use InputStreams
      or File Descriptors. Later is being used out of the two.
      # Conflicts:
      #	libs/ui/KisMainWindow.cpp
  25. 11 Sep, 2020 2 commits
  26. 10 Sep, 2020 1 commit
  27. 12 Aug, 2020 1 commit
  28. 08 Aug, 2020 1 commit
    • Tusooa Zhu's avatar
      Fix ref images layer not shown after switching snapshot · 29e666f9
      Tusooa Zhu authored
      [1] The fix for a crash when loading a file with ref images in
      used layer->extent() as a criterion for judging whether "the layer is loaded."
      However, this criterion is not correct because the real cause of the crash is
      KisView's d-pointer is not yet initialized, when KisReferenceImagesDecoration
      is being constructed, which is called by the ctor of KisView::Private.
      [2] layer->extent() is always empty so the current situation is
      KisReferenceImagesDecoration::setReferenceImageLayer() is never called,
      due to the criterion in [1].
      [3] This fix added an argument, viewReady, to the constructor of
      KisReferenceImagesDecoration, so that when it is being called from
      KisView::Private's constructor, it will not try to update the canvas
      because that leads to problems.
      [4] In setReferenceImageLayer, I also modified the logic to not
      try to dereference a weak pointer before verifying its validity.
      If I do not do so, it will trigger an assert.
      BUG: 420051
  29. 07 Aug, 2020 1 commit
  30. 06 Aug, 2020 1 commit
  31. 04 Aug, 2020 1 commit
  32. 02 Jul, 2020 1 commit
  33. 20 Jun, 2020 1 commit
  34. 09 Jun, 2020 1 commit
  35. 27 May, 2020 1 commit