Range validation for typed spin values
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AirDC++ |
Confirmed
|
Low
|
Unassigned |
Bug Description
I can type in 0 in all the values (see zeros.jpg) in "Disconnect slow downloads" and when i press OK it will change some of the value to 1 (see ok.jpg).
If i use the arrows to change it i can set some of them to 0, but not all (arrows.jpg) and when i press OK it will change to the same value as the ok.jpg. It's "Disconnect downloads if speed is below" that will change from 0 to 1.
If 0 is not a valid value it should not be possible to type in 0 or use the arrows to set it to 0 value.
This is not the first time i have reported this and if you want to decrease the amount of bugs you should take this more seriously and stop the user from using illegal values. I know 0 is not illegal every where but if it is it should also be impossible for the user to write 0 both manually or if he use the arrows.
Hmm, i could only attach one file :(
I'll attach the other two pictures by adding a comment.
Changed in airdcpp: | |
status: | New → Confirmed |
importance: | Undecided → Low |
summary: |
- Disconnect slow downloads and the value 0 + Range validation for typed spin values |
I forgot to mention that if i set them all at 0 and press one arrow up some of them will jump to 2 instead of 1.
This indicate that something is wrong.