1. 22 Apr, 2019 2 commits
  2. 12 Mar, 2019 1 commit
    • Agata Cacko's avatar
      Fix adding files to Recent Documents · 3c0ab08d
      Agata Cacko authored
      Because of typo files were added to Recent Documents
      every time it wasn't needed and not added when it was
      needed. This commit makes adding files to Recent Documents
      consistent with the intent.
      
      BUG:405364
      3c0ab08d
  3. 11 Mar, 2019 1 commit
    • Agata Cacko's avatar
      Fix loading wrong file format (progress bar + recent docs) · 52ee93a9
      Agata Cacko authored
      Summary:
      Before this patch, when you forced Krita to load file in
      unknown format, it showed uncancelled progress bar and
      showed the file in Recent Documents.
      It happened when you dragged and dropped file to the
      welcome screen or import animation frames or use Open->File
      or Open -> Recent Files.
      Progress bars were visible only when some image was opened.
      This commit cancels progress bars and make sure unloadable
      files are not added to Recent Documents.
      
      CCBUG:402625
      
      Test Plan:
      1. Create an unloadable file. Can be "touch a".
      2. Load it using one of the ways mentioned above
      3. After loading, there is an error message. Click ok.
      4. If you used Import Animation Frames, look at the bottom
      of Krita window.
      - before: progress bar still "loading"
      - now: no progress bar visible
      5. If you used other option, create a new file or open
      something else, and you'll see the same effect.
      6. Look at Recent Documents.
      - before: unloadable file added to list
      - now: no unloadable file added to list
      (beside the ones that were aleady there after testing)
      
      Reviewers: #krita, rempt
      
      Reviewed By: #krita, rempt
      
      Tags: #krita
      
      Differential Revision: https://phabricator.kde.org/D19611
      52ee93a9
  4. 22 Feb, 2019 1 commit
    • Anna Medonosova's avatar
      Saving Mirror Tool state to KRA · 54d3dc15
      Anna Medonosova authored
      Summary:
      Saving Mirror Tool state to KRA file, wished for in bug 339515.
      
      BUG:339515
      
      Test Plan:
        - Set up mirror lines. Save, close and reopen. Expected result: the mirror lines and options should be automatically set and activated.
        - Open multiple files, with and without mirror lines. Expected result: Every open document should have separate configuration. Toolbar actions should affect only the currently active view.
      
      Reviewers: #krita, rempt
      
      Reviewed By: #krita, rempt
      
      Subscribers: rempt
      
      Tags: #krita
      
      Differential Revision: https://phabricator.kde.org/D18254
      54d3dc15
  5. 19 Feb, 2019 1 commit
  6. 05 Feb, 2019 1 commit
    • Halla Rempt's avatar
      Add usage logging to the buginfo dialog · caebac3e
      Halla Rempt authored
      We can now log important events to a krita.log file. It is completely
      independent of qDebug, and only meant for those actions that we know
      users often get wrong or have problems with. Right now, it logs
      creating, loading, exporting and saving a file, and switching between
      the smoothing options.
      
      The krita.log file is NOT automatically uploaded or shared or anything
      like that. The header that explains this is translated so users can
      see that for themselves.
      
      We rotate 10 sessions in the log file, so even if the user starts Krita
      a few times after having a problem, we should still be able to review
      the problematical session.
      
      The logging api is pretty simple: a static KisUsageLogger::log method
      that writes a timestamp, and a KisUsageLogger::write method that writes
      an informational line without a timestamp.
      
      Note that the logger is created and torn down in the main function:
      this means that the location is GenericDataLocation, not AppDataLocation.
      
      CCMAIL:kimageshop@kde.org
      caebac3e
  7. 16 Dec, 2018 1 commit
    • Eoin O'Neill's avatar
      Added Fill Layer Content Option for New Documents · cb8d3c97
      Eoin O'Neill authored
      This patch also changes a few things about how new images are created by
      making use of enums in the newImage interface. I think I've also
      addressed the background opacity in a way that makes more sense and also
      allows for users to tweak background opacity settings after creating a
      new image. Lastly, while using RASTER or FILL backgrounds, if you create
      more than one layer the background layer will start locked. This helps
      to prevent accidental painting on initial starting background layers.
      cb8d3c97
  8. 31 Oct, 2018 1 commit
  9. 07 Oct, 2018 1 commit
  10. 27 Sep, 2018 1 commit
  11. 17 Sep, 2018 1 commit
  12. 13 Sep, 2018 2 commits
    • Dmitry Kazakov's avatar
      Reset modified state of the recovered files correctly · 75c39f3f
      Dmitry Kazakov authored
      KUndo2Stack doesn't emit any signals if it is empty, so
      we should take care about that separately.
      75c39f3f
    • Dmitry Kazakov's avatar
      Fix removing of autosave files in some cases · bbcde723
      Dmitry Kazakov authored
      1) When we recover some file, then discard it by closing
         without saving, then this file should be removed.
      
      2) When saving a file with a different name, the autosave
         files for the old name should be removed.
      
      3) KisMainWindow should not touch url text and recovered
         state of the file, it is correctly set by the document
         itself now
      bbcde723
  13. 06 Aug, 2018 1 commit
  14. 05 Aug, 2018 1 commit
  15. 31 Jul, 2018 1 commit
    • Halla Rempt's avatar
      Create vector selections and layers are created with a KoShapeControllerBase · e4e21bb9
      Halla Rempt authored
      A KoShapeControllerBase (formerly known as KoShapeBasedDocumentBase)
      is necessary otherwise KoShapeController::resourceManager might return
      0, which causes asserts and crashes. So, pass the KoShapeControllerBase
      down all the way from KisShapeLayer and KisShapeSelection.
      
      This fixes the KisKraSaverTest
      e4e21bb9
  16. 24 Jul, 2018 2 commits
  17. 23 Jul, 2018 2 commits
  18. 17 Jul, 2018 1 commit
  19. 10 Jul, 2018 1 commit
  20. 09 Jul, 2018 1 commit
  21. 04 Jul, 2018 1 commit
  22. 26 Jun, 2018 3 commits
    • Dmitry Kazakov's avatar
      Fix initialization of the global assistants color · 9e7e0e0c
      Dmitry Kazakov authored
      1) KisDocument is a 'model' of global color
      2) KisPaintingAssistantsDecoration is a 'controller' of global color
      3) KisPaintingAssistant is a 'view' of global color
      
      Decoration is responsible for updating the global color cache
      of global color in all the assistants.
      9e7e0e0c
    • Dmitry Kazakov's avatar
      Save global color to KRA file · a4708fcd
      Dmitry Kazakov authored
      Summary:
      This is a patch on top of my custom colors patch.
      
      The shared/global assistant color for painting assistants is stored outside of the assistant data model. Because of this I had to add a new property to save to in the KRA saver and loader.
      
      I also had to fix up a few initialization areas in the UI so the loaded values didn't get wiped out.
      
      I also removed a couple "legacy" comments in the KRA saver that got me confused. boud confirmed that those notes were in the calligra days
      
      Test Plan:
      Have multiple assistants. A couple with a shared color and one with a custom color.
      
      Saved and loaded the file and made sure it kept the same value.
      
      Reviewers: #krita, dkazakov
      
      Subscribers: dkazakov
      
      Tags: #krita
      
      Differential Revision: https://phabricator.kde.org/D13437
      a4708fcd
    • Jouni Pentikäinen's avatar
      Fix reference image layer lifetime · b6294fe4
      Jouni Pentikäinen authored
      b6294fe4
  23. 25 Jun, 2018 2 commits
    • Dmitry Kazakov's avatar
      Fix initialization of the global assistants color · 4dc097c9
      Dmitry Kazakov authored
      1) KisDocument is a 'model' of global color
      2) KisPaintingAssistantsDecoration is a 'controller' of global color
      3) KisPaintingAssistant is a 'view' of global color
      
      Decoration is responsible for updating the global color cache
      of global color in all the assistants.
      4dc097c9
    • Dmitry Kazakov's avatar
      Save global color to KRA file · 67823cd5
      Dmitry Kazakov authored
      Summary:
      This is a patch on top of my custom colors patch.
      
      The shared/global assistant color for painting assistants is stored outside of the assistant data model. Because of this I had to add a new property to save to in the KRA saver and loader.
      
      I also had to fix up a few initialization areas in the UI so the loaded values didn't get wiped out.
      
      I also removed a couple "legacy" comments in the KRA saver that got me confused. boud confirmed that those notes were in the calligra days
      
      Test Plan:
      Have multiple assistants. A couple with a shared color and one with a custom color.
      
      Saved and loaded the file and made sure it kept the same value.
      
      Reviewers: #krita, dkazakov
      
      Subscribers: dkazakov
      
      Tags: #krita
      
      Differential Revision: https://phabricator.kde.org/D13437
      67823cd5
  24. 19 Jun, 2018 1 commit
  25. 01 Jun, 2018 1 commit
  26. 30 May, 2018 1 commit
  27. 19 May, 2018 2 commits
    • Dmitry Kazakov's avatar
      Fix autosave never save stuff because the image is too busy · 4b4cd75b
      Dmitry Kazakov authored
      Now the strategy is the following:
      
      1) Wait default time period for autosave
      2) Check if the image is busy
      3) If the image is not busy, just save :)
      4) If the image is busy, do three tries with emergency
         interval (10 ms each). If all the tries are failed,
         post a background stroke which will run after the current
         stroke and initiate the autosave.
      4b4cd75b
    • Dmitry Kazakov's avatar
      Fix autosave never save stuff because the image is too busy · 4aa690de
      Dmitry Kazakov authored
      Now the strategy is the following:
      
      1) Wait default time period for autosave
      2) Check if the image is busy
      3) If the image is not busy, just save :)
      4) If the image is busy, do three tries with emergency
         interval (10 ms each). If all the tries are failed,
         post a background stroke which will run after the current
         stroke and initiate the autosave.
      4aa690de
  28. 16 Apr, 2018 1 commit
  29. 03 Apr, 2018 2 commits
  30. 28 Mar, 2018 2 commits