#294 closed bug (fixed)
BSlider behavor
| Reported by: | diver | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Try to open Diskprobe with some file and drag slider to the right outside diskprobe window. Slider will come back to it's 1st position, but should be in the end of that scale.
Change History (8)
comment:1 by , 19 years ago
| Summary: | BSlider behavor → BSlider behavor |
|---|
comment:2 by , 19 years ago
| Component: | Kits → Applications |
|---|
comment:3 by , 19 years ago
comment:4 by , 19 years ago
| Owner: | changed from to |
|---|
comment:5 by , 19 years ago
| Status: | new → closed |
|---|
comment:6 by , 19 years ago
| Resolution: | → fixed |
|---|
comment:7 by , 19 years ago
It was a bug in BSlider - almost naturally, since it worked perfectly fine in R5 :) You were right though, the int32 got too big, but not from DiskProbe, but from BSlider::ValueForPoint() which did not work correctly for these large values. Fixed in hrev16839.
comment:8 by , 19 years ago
| bug_group: | → developers |
|---|
Note:
See TracTickets
for help on using tickets.
The int32 used for SetValue() overflows, that's all. It's not a bug in BSlider.