Members of the KDE Community are recommended to subscribe to the kde-community mailing list at https://mail.kde.org/mailman/listinfo/kde-community to allow them to participate in important discussions and receive other important announcements

  1. 16 Aug, 2019 1 commit
  2. 15 Aug, 2019 1 commit
    • Agata Cacko's avatar
      Fix Strength not used in Rotation - Fuzzy Dab · 3602c724
      Agata Cacko authored
      Before this commit, if you chose Fuzzy Dab sensor
      in Rotation option, the value of the Strength slider wouldn't
      affect the resulting rotation of the brush tip.
      This commit fixes that behaviour: now if you choose very low
      Strength and the first curve from the template ones,
      the brush tip will rotate only slightly (before it would rotate
      within the full 360* range).
      
      * Fuzzy Dab is 'additive' kind of sensor, so it's value would be put
      in 'realAdditivePart' in rotationLikeValue(). 'constant' contains the
      value of 'Strength' slider. To get it working together,
      'realAdditivePart' had to be multiplied by the 'constant' value.
      
      * HSV option just ignored the problem and multiplied it by the value of
      the slider later. It couldn't be done for Rotation because Rotation
      takes the canvas rotation into account (see rotationLikeValue).
      Therefore it had to be done inside rotationLikeValue function, not
      later. Therefore the multiplication in HSV option had to be disabled
      to not double the effect.
      
      BUG:376179
      BACKPORT:krita/4.2
      3602c724
  3. 14 Aug, 2019 2 commits
    • Agata Cacko's avatar
      Fix curve change despite 'Use same curve' checked · 47a57162
      Agata Cacko authored
      Before this commit, if you have a preset like Fill_circle
      that has "Use the same curve" checkbox checked and you were
      clicking on other sensors, the curve would be back to the default
      curve (the one that other sensors had) if you switch back and forth
      between some sensors (like Pressure -> X-Tilt-> Pressure).
      
      Also before this commit if you have the default uprising curve
      and you switched Rotation -> Tilt elevation, the curve would change.
      
      This commit fixes both behaviours (first by adding transferCurve(),
      second by switching the line in kis_curve_widget).
      
      This commit also includes two slot functions instead of one function
      that were used as a slot for two different signals. It helps with
      debugging signals and keeping stuff clear and ordered.
      
      There is one problem left: if you switch Tilt elevation -> Distance
      (using the 'hill' curve), the preset is set to modified even though
      the curve doesn't change.
      
      BUG:383909
      BACKPORT:krita/4.2
      47a57162
    • Dmitry Kazakov's avatar
      Fix Shift and Alt modifiers in OUtline Selection Tool · bd06296f
      Dmitry Kazakov authored
      We should pass the keys to the tool, even when it is not active
      to make sure its keyPress/keyRelease methods work fine. To make
      it works we need to initialize the environment correctly in
      KisToolInvocationAction::processUnhandledEvent;
      
      BUG:410532
      BACKPORT:krita/4.2
      bd06296f
  4. 13 Aug, 2019 8 commits
  5. 12 Aug, 2019 3 commits
    • Karl Ove Hufthammer's avatar
      Remove misleading ‘px’ suffix for ‘move amount’ shortcut setting · ed33edf2
      Karl Ove Hufthammer authored
      The ‘Amount’ input field for the move tool had a ‘px’ suffix.
      But the unit used is chosen from a different dropdown field,
      so the input field could end up saying ‘0.3527px’ ‘Millimeters (mm)’,
      which didn’t make sense. Also updated the tooltip to reflect that
      the unit can be chosen by the user.
      ed33edf2
    • Dmitry Kazakov's avatar
      Fix lags in Move Tool when using tablet device · dcdef2ea
      Dmitry Kazakov authored
      Now the Move Tool uses the same FSP-limiting compression as the freehand
      tool does. The relevant code has been moved into a special class
      KisAsyncronousStrokeUpdateHelper, which implements a logic of issuing
      threshold events.
      
      Bascially, all the sources of event (tablet move and async update from
      KisAsyncronousStrokeUpdateHelper) now try to initiate a canvas update.
      If enough time has passed and previous updates has finished, then a new
      update is started.
      
      One more important change: now actual layer offset change is executed in
      the same exclusive job as the updates (with limited FPS), therefore, it
      avoids garbage-looking leftovers of the intemediate move states.
      
      BUG:410838
      dcdef2ea
    • Scott Petrovic's avatar
  6. 09 Aug, 2019 1 commit
  7. 07 Aug, 2019 2 commits
  8. 05 Aug, 2019 2 commits
  9. 04 Aug, 2019 2 commits
  10. 02 Aug, 2019 7 commits
  11. 01 Aug, 2019 4 commits
  12. 31 Jul, 2019 1 commit
  13. 30 Jul, 2019 6 commits
    • Dmitry Kazakov's avatar
      Make shape painting tools unblocking (use strokes) · 008503fb
      Dmitry Kazakov authored
      Opening a waiting dialog may make the shortcuts matcher unhappy,
      so we should avoid that.
      
      CCBUG:409968,408826,409275
      008503fb
    • Dmitry Kazakov's avatar
    • Dmitry Kazakov's avatar
      Make KisToolTransform fully asynchronous · eb17ce74
      Dmitry Kazakov authored
      Now all initialization of the transform tool has been moved into the
      stroke's context. It means that the tool doesn't need to block event
      loop until it image is finished anymore.
      
      The fix uses he new features of the strokes framework, specifically
      mutated stroke jobs.
      
      CCBUG:409275
      eb17ce74
    • Dmitry Kazakov's avatar
      Make Move Tool asynchronous · 21889437
      Dmitry Kazakov authored
      Calling blockUntilOperationsFinished() from tool event handler makes
      KisShortcutMatcher to be entered recursively. It basically breaks events
      flow and makes KisShortcutMatcher crazy.
      
      I tried to move blocking into the shortcuts matcher itself (so that
      it could treat recursive entrance correctly), but it doesn't handle
      special cases like KisToolTransform::activate(), which should also
      block (if we keep them blocking).
      
      CCBUG:409275
      21889437
    • Karl Ove Hufthammer's avatar
      Improve label for input field for number of raindrops · 26e236d5
      Karl Ove Hufthammer authored
      The label for the ‘number of raindrops’ input field just said,
      ‘Number’. But the string ‘Number’ is also used, with a different
      meaning, in the metadata editor, making it difficult to provide
      a translation that worked for both strings. The raindrop label
      has therefore been changed to ‘Number of drops’, which is also
      easier to understand.
      26e236d5
    • Karl Ove Hufthammer's avatar
      Make ‘Random Noise’ filter name consistent · af50061b
      Karl Ove Hufthammer authored
      In the filter menu, the filter was called ‘Random Noise’,
      but in the filter dialogue, it was called just ‘Noise’.
      Now it’s ‘Random Noise’ in both places.
      af50061b