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=80323 --- shadow/80323 2006-12-20 09:34:01.000000000 -0500 +++ shadow/80323.tmp.10962 2006-12-20 11:34:18.000000000 -0500 @@ -1,12 +1,12 @@ Bug#: 80323 Product: Mono: Class Libraries Version: 1.2 OS: other OS Details: SUSE 10.1 -Status: NEW +Status: ASSIGNED Resolution: Severity: Unknown Priority: Normal Component: libgdiplus AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] @@ -52,6 +52,28 @@ Created an attachment (id=18351) ColorMatrix bug test case - binary and source ------- Additional Comments From [EMAIL PROTECTED] 2006-12-20 06:23 ------- --> Windows.Forms + +------- Additional Comments From [EMAIL PROTECTED] 2006-12-20 11:34 ------- +The problem seems to be that the (current) code works on ARGB while +the bitmap itself isn't (really) using alpha (i.e. the original color +100,255,0,0 is transformed into 255,255,155,155 on both Mono and MS). + +Mono +Bitmap.GetPixel (50,50) = Color [A=255, R=255, G=155, B=155] +Bitmap.GetPixel (150,50) = Color [A=255, R=255, G=255, B=255] + +MS +Bitmap.GetPixel (50,50) = Color [A=255, R=255, G=155, B=155] +Bitmap.GetPixel (150,50) = Color [A=255, R=255, G=205, B=205] + +Applying the (current) calculation on the original (100,255,0,0) color +looks good (i.e. the algo doesn't match the data). + +For the blue background I suspect the calculations (including +float/int conversions) are introducing small variations that gets +amplified at each iteration. + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
