[Mono-bugs] [Bug 643366] [Regression] Scrollbar: "LargeChange" System.ArgumentOutOfRangeException

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=643366

https://bugzilla.novell.com/show_bug.cgi?id=643366#c3


Hin-Tak Leung <htl10 at users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[Regression?] Scrollbar:    |[Regression] Scrollbar:
                   |"LargeChange"               |"LargeChange"
                   |System.ArgumentOutOfRangeEx |System.ArgumentOutOfRangeEx
                   |ception                     |ception

--- Comment #3 from Hin-Tak Leung <htl10 at users.sourceforge.net> 2010-10-06 11:52:29 UTC ---
I can definitely state that it is a regression now - if I overwrite

C:/Program
Files/Mono-2.8/lib/mono/gac/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

with the 2.6.7 version:

C:/Program
Files/Mono-2.6.7/lib/mono/gac/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

The LargeChange exception pop-up problem goes away; also the Log section's text
reappears. So it looks like there are two visible regressions - the LargeChange
exception pop-up and the Log section text disappearing.

According to git log, there are only about 40 commits which affects
System.Windows.Forms between 2.6.7 and 2.8? I'd do a git-bisect if there is a
simple way of cross-compiling just that dll - there doesn't seem to be a easy
way of just building that part.

I was looking at the git commit log, could the Log section be a DataGrid or
something related?

-- 
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.