Closed eyeonus closed 4 years ago
Sounds like a good idea!
I remember when I worked on this, debating which way it should spin - the issue was over "natural scrolling" on my MacBook - where the touchpad scroll direction matches the direction you get on a touchscreen device...
Anyway, I'll make the change you've requested.
Awesome-sauce.
You can now set a reverse
property when adding a spin box
After Commenting Out the lines as suggested by eyeonus it works for me. Can you explain to me how your solution works? I tried: .changeSpinBox(title, vals, reverse=True) Replaces the contents of the specified SpinBox with the new vals. Set reverse to False if you don;t ant to reverse the values.
from the docs but I could not get it working.
I think you have to do it when creating the SpinBox, but you're trying to modify an already existing one?
Context
Currently the spinBar is hard-coded to behave in a, to me at least, very strange way:
Pressing the down arrow makes the number go up.
I noticed when trying to figure out why this was so that there is a variable that is not exposed called "reverse", and which is always set to True in the very few methods it is used in.
My request is to make this argument available at the API level, with the effect of toggling the execution of the indicated code in the snippet below.
Expected Behaviour
https://youtu.be/2lzCEWj6dac
This behaviour is achieved by making the following changes in appJar:
Actual Behaviour
https://youtu.be/KZKaJ4yZARE
Sample code, demonstrating the issue
What steps are needed to reproduce the bug
Create a SpinBox. Any SpinBox. This behaviour is intrinsic.
Version Information