[krita] [Bug 498817] Curve points bug
https://bugs.kde.org/show_bug.cgi?id=498817 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #3 from [email protected] --- *** Bug 520188 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 498817] Curve points bug
https://bugs.kde.org/show_bug.cgi?id=498817 Freya Lupen changed: What|Removed |Added CC||[email protected] --- Comment #2 from Freya Lupen --- It has to do with some of the sensors having different x ranges. Seems like the spinbox values are getting bounded to the new min/max before the value is converted to the new range. For instance, switching to X-/Y- Tilt makes the active point's x -60 (0%). Tilt has a maximum of 0, so the old value from another sensor gets changed to 0. Then, KisCurveWidgetControlsManager is still using the old range of 0 to 100 or whatever, so it ends up as 0% (rather than 100%). Then setting tilt to something and switching to another sensor makes the active point's x 100%. Everything else has a minimum of 0, so our negative value gets set to that. But the manager's still using the old range of -60 to 0, to it gets turned into 100% (rather than 0%). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 498817] Curve points bug
https://bugs.kde.org/show_bug.cgi?id=498817 [email protected] changed: What|Removed |Added Status|REPORTED|CONFIRMED Keywords||triaged CC||[email protected] Ever confirmed|0 |1 --- Comment #1 from [email protected] --- Okay, finally made sense of this report thanks to this thread: https://krita-artists.org/t/bug-with-fuzzy-dab/170284 Steps to reproduce: 1. Pick a pixel brush engine. 2. Pick some option with dynamics, like Size or Ratio. 3. Enable pen settings. 4. Enable "Share curve across all settings" 5. Enable a single dynamic. 6. Adjust the curve. 7. Switch to a different dynamic. 8. Switch back to the original dynamic. Expected result: the curve still looks the same. Actual result: the curve gets messed up in a seemingly random way. -- You are receiving this mail because: You are watching all bug changes.
