https://bugs.kde.org/show_bug.cgi?id=429063
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #5 from Nate Graham <n...@kde.org> ---
Re-opening since the fix was reverted. See Bug 430050.
I'm copying David Edmundson's comment over there about options to fix this
without regressions:
In terms of moving forward and options within the current code.
Option 1:
Go with your original patch in frameworks. This must remain an exception and
not a rule.
Guard usage on the client side with
`
Component.onCompleted: if
(self.hasOwnProperty("reverseDragAndScrollDirections")) {
self.reverseDragAndScrollDirections = true;
}
`
so it's backportable and won't break when we move to generic styles.
and drop the stepSize change
Option 2:
Same but in reverse. Have the style query
`control.hasOwnProperty("reverseDragAndScrollDirections") &&
control.reverseDragAndScrollDirections`
Then declare that as a new property in the panel's spinbox.
It'd be closer to how Breeze does additional things from widget controls
Option3:
Spinbox.down.indicator is public API, we can re-implement the relevant FrameSVG
code, but swap the +/-
and keep the current negative stepsize
Option4:
override contentItem inside the panel
and keep the current negative stepsize
--
You are receiving this mail because:
You are watching all bug changes.
