[Mono-bugs] [Bug 403122] New: Scrollbar: crashing and bad maths
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Tue Jun 24 05:11:14 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=403122
Summary: Scrollbar: crashing and bad maths
Product: Mono: Class Libraries
Version: 1.9.0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Windows.Forms
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: andyhume32 at yahoo.co.uk
QAContact: mono-bugs at lists.ximian.com
Found By: ---
I noticed that the LargeChange value is bounded to the Maximum value, it should
be bounded to the length of the scrollbar, i.e. Max-Min+fudge. For instance
with give Min,Max pair, should see:
-50, 50 -> maximum LargeChange = 101
199, 200 -> maximum LargeChange = 2
200, 200 -> maximum LargeChange = 1
But instead bounded to 51, 201, 201, respectively.
And behaviour is thus wrong too, for instance in case 1 that Scrollbar tab
won't move by arrow or bar click, the tab can be dragged, but value is always
-49.
Also scrollbar is crashable in various circumstances. For instance:
Defaults values are: min,max: 0,100; changes: 1,10
Set Maximum to 8.
Click the scrollbar's right (/down) arrow. Crash:
[[
Unhandled Exception: System.ArgumentOutOfRangeException: '-1' is not a valid
value for 'Value'. 'Value' should be between 'Minimum' and 'Maximum' [@0->-1
0<->8 1_9]
Parameter name: Value
at System.Windows.Forms.ScrollBar.set_Value (int) [0x00167] in
D:\cygwin\usr\src\mono\mcs\class\Managed.Windows.Forms\System.Windows.Forms\ScrollBar.cs:623
at System.Windows.Forms.ScrollBar.SmallIncrement () [0x00031] in
D:\cygwin\usr\src\mono\mcs\class\Managed.Windows.Forms\System.Windows.Forms\ScrollBar.cs:1301
at System.Windows.Forms.ScrollBar.OnMouseUpSB
(object,System.Windows.Forms.MouseEventArgs) [0x000b7] in
D:\cygwin\usr\src\mono\mcs\class\Managed.Windows.Forms\System.Windows.Forms\ScrollBar.cs:1187
]]
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list