[Mono-bugs] [Bug 440220] New: Multiple faults in ProgressBar: ForeColor, negative Step, missing/wrong exceptions

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Oct 30 10:52:03 EDT 2008


           Summary: Multiple faults in ProgressBar: ForeColor, negative
                    Step, missing/wrong exceptions
           Product: Mono: Class Libraries
           Version: 2.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: ---

Created an attachment (id=248880)
 --> (https://bugzilla.novell.com/attachment.cgi?id=248880)
Source to ProgressBar test app

Enough of looking for one fault after another!  Attached is a test application
for ProgressBar that attempts to cover all cases (within reason!).  That covers
the stuff that needs to be checked by eye[1], and additional unit-tests for the
other stuff.

This exposes multiple bugs:
1. ForeColor is ignored.
2. PerformStep does nothing when Step is negative.  Causes a unhandled
exception when big numbers are used.
3. No bounding of Maximum is done when Minimum is set and vice versa.
4. Wrong exceptions produced in FX2 when setting invalid Value/Maximum/Minimum
5. Changing the Style property does not update the control immediately; a
forced repaint is required.
6. Marquee speed is very weird, changing between very very fast and very very
very very fast, and in inverse to the speed setting?
7. Also while running the app I saw an infinite loop within DrawProgressBar. 
On investigation this occurs when ProgressBar.set_Height=1.  Best verified in
PropGridFormControlsTabView, set Value=50 (etc), set Height=1 -> hang!  Occurs
in Blocks style only in non-VisualStyles mode.  I'll add unit-tests for it once
its fixed.
8. Missing exceptions when setting invalid Style and similar.

(EnableVisualStyles=Yes is good on Windows, but of course not 100% pass on

[1] In hindsight in the app there's too much testing of the set_Value and
Increment/PerformStep don't, unit-tests of that would have done.

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