1. 09 Feb, 2019 1 commit
  2. 08 Feb, 2019 1 commit
    • Ashwin  Dhakaita's avatar
      Fixed canvas isn't cleared when adding a new blank frame · ab53dc16
      Ashwin Dhakaita authored
      Summary:
      When create blank frame is clicked on animation docker having a  keyframe selected, that is not the last frame in the timeline, the canvas is not cleared properly.
      
      Note from Dmitry Kazakov: setDirty() should be called **after** the
      actual device change has been done. Otherwise race condition may happen.
      
      BUG:    403535
      FIXED-IN:    krita 4.2.0-pre-alpha (git 0d8b6bd6)
      Reviewers: #krita, dkazakov!
      Subscribers: dkazakov
      Tags: #krita
      Differential Revision: https://phabricator.kde.org/D18790
      ab53dc16
  3. 07 Feb, 2019 4 commits
  4. 06 Feb, 2019 3 commits
  5. 05 Feb, 2019 2 commits
    • Harald Sitter's avatar
      fix/update snap & port to core18 & depend on neon packages for newer tech · 2d4a5a53
      Harald Sitter authored
      Summary:
      this is largely a partial sync from the kf5 launcher used for the kf5
      content snap.
      
      launcher:
      - make sure all lib paths are in ld_library
      - make sure GL drivers may be found
      - make sure nvidia host-mounted drivers may be found
      - rejigger font handling to sit on top of the host fonts instead of
        shipping ones inside the snap
      - XDG variables are no longer separated by version (the individual HOMEs
        are already by version e.g. ~/snap/krita/{1,2,3}) so the additional
        versioning only serves to lose all settings on updates
      - set more XDG variables to ensure they are sound
      - force qtchooser to use suitable paths directed at the snap
      - do not hardcode any SESSION variables or platformtheme. the variables
        are forwarded into the snap, and Qt will figure out what to do with the
        environment on its own
      - do not attempt to start KIO slaves via klauncher but instead qprocess
        fork them (ensures a) not breaking out b) they are in the same pgroup)
      - configure qlibraryinfo to find relevant Qt stuff from the snap (this
        relies on a neon specific patch in qtbase to make QLI XDG-aware)
      - translations are now working, alas, at a cost to startup performance as we
        need to generate locales on-demand (it may be prudent to pre-generate
        some popular locales) to reduce overhead when they are used, at the cost of
        snap size. this is actually implemented by kf5-locale-gen which generates
        locales in the snap's home and directs glibc there
      - the launcher now forces plasma theme plugin on all platforms, this is
        specifically to ensure that the app is fully functional and in fact looks
        good. this may be revisted once desktop portals are fully available (qt 5.12
        and portal SRU into ubuntu 16.04), but even so certain qstyles are
        not working very well I've been told
      
      snap:
      - now on core18 (i.e. ubuntu 18.04 base)
      - use desktop and desktop-legacy interfaces, the former gives approximately
        what unity7 does but is directed at the future, the latter is somewhat
        terribly named because it actually gives access to some key dbus
        interfaces, such as accessibility and input methods (legacy may be
        done away with in the future if desktop can grow better confinement
        rules)
      - do away with the part separation between kdeframeworks and qt, since
        both are only stage packages there isn't much use derived from them
        besides blowing up the yaml
      - all packages have been updated to 18.04 variants
      - fonts are no longer being staged (launcher now picks up system fonts)
      - new plasma-integration part makes sure krita neatly integrates into
        plasma environments
      - setup/ is now snap/ [former is deprecated, same functionality]
      - build is now done in release mode instead of manually setting compile
        flags
      
      build:
      - to get a newer qt/kf5 stack the snap is using neon builds instead of
        ubuntu 16.04 builds
      - to properly build, build.sh should be used (which depends on lxd to
        provision an ephemeral build container with snapd)
      
      Test Plan: builds a snap!
      
      Reviewers: #krita, rempt
      
      Reviewed By: #krita, rempt
      
      Tags: #krita
      
      Differential Revision: https://phabricator.kde.org/D18722
      2d4a5a53
    • Boudewijn Rempt's avatar
      Add usage logging to the buginfo dialog · caebac3e
      Boudewijn 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
  6. 04 Feb, 2019 1 commit
  7. 01 Feb, 2019 12 commits
  8. 31 Jan, 2019 3 commits
  9. 30 Jan, 2019 3 commits
  10. 29 Jan, 2019 3 commits
    • Eoin O'Neill's avatar
      Added Real-Time Preview when Changing Generator Layer Properties. · f63db12b
      Eoin O'Neill authored
      Colors and patterns will update when changing the values within the
      properties window of a generator layer. The changes will only be registered
      with the undo command system when accepting the change. Canceling your changes
      will revert the layer back to the state before the properties panel was opened.
      
      This should make changing the fill layer color a more artistic process,
      letting you visually see the effects before applying the change.
      f63db12b
    • Eoin O'Neill's avatar
      Changed The Properties for Generator (Fill) Layers to be Non-Modal · 1272564e
      Eoin O'Neill authored
      This change moves toward consistency with other properties windows
      allowing you to move the properties window of a fill layer. The new window
      can be called either as modal or non modal depending on whether or not it has
      existing layer data passed into it. This means that creating a new fill layer
      uses a modal window while editing allows you to move the window to the side to compare
      and contrast values.
      1272564e
    • Eoin O'Neill's avatar
      Revert Patch D18462 · ef1ece55
      Eoin O'Neill authored
      Patch for review D18462 snuck into commit cf5346cb. This reverts the
      patch to restore original fill color window behavior.
      ef1ece55
  11. 28 Jan, 2019 3 commits
  12. 27 Jan, 2019 1 commit
  13. 26 Jan, 2019 3 commits