Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78371 --- shadow/78371 2006-05-11 14:41:34.000000000 -0400 +++ shadow/78371.tmp.21150 2006-05-12 09:23:00.000000000 -0400 @@ -1,14 +1,14 @@ Bug#: 78371 Product: Mono: Class Libraries Version: unspecified -OS: +OS: unknown OS Details: Status: NEW Resolution: -Severity: +Severity: Unknown Priority: Normal Component: Windows.Forms AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- @@ -29,6 +29,25 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-05-11 14:41 ------- Created an attachment (id=16996) Test case + +------- Additional Comments From [EMAIL PROTECTED] 2006-05-12 09:22 ------- +Did some testing. The StatusBar code is absolutely ok. + +It is the speed of the drawing methods in Graphics that hurts the +StatusBar performance (aka cairo). + +If you comment + +dc.DrawString (text, panel.Parent.Font, br_forecolor, r, string_format); + +in ThemeWin32Classic.DrawStatusBarPanel it saves about 9 seconds for +the test app on my system. + +Commenting the DrawLine code in CPDrawBorder3D saves another 7 seconds + and finally commenting CPDrawSizeGrip and the test app needs only 1.2 +seconds to run the loop. + +Oh cairo.... _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
