https://bugs.kde.org/show_bug.cgi?id=498817
Freya Lupen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Freya Lupen <[email protected]> --- 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.
