[Mono-bugs] [Bug 58885][Nor] Changed - Graphics class is drawing with wrong colors

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 26 May 2004 16:01:38 -0400 (EDT)

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 domo@domnanovits.at.


--- shadow/58885	2004-05-26 11:57:36.000000000 -0400
+++ shadow/58885.tmp.18153	2004-05-26 16:01:38.000000000 -0400
@@ -100,6 +100,30 @@
 sorry, first do cvs update for libgdiplus, then copy the line I have
 given above and then build libgdiplus.
 ------- Additional Comments From gonzalo@ximian.com  2004-05-26 11:57 -------
 About Color.Green, we should use the same as MS does. I sent an email
 to ravindra on this.
+------- Additional Comments From domo@domnanovits.at  2004-05-26 16:01 -------
+I have added the printf command to the latest libgdiplus source. Here are the results from 
+the tests. The first line displays the ARGB properties of the managed Color structure, the 
+second the output from the new printf line. So far everythings seems to be in order. I fear 
+the error is in far deeper regions.
+Mono Color value: A=255, R=0, G=0, B=255, argb=-16776961
+libgdiplus: a=255.000000, r=0.000000, g=0.000000, b=255.000000
+Mono Color value: A=255, R=255, G=0, B=0, argb=-65536
+libgdiplus: a=255.000000, r=255.000000, g=0.000000, b=0.000000
+Mono Color value: A=255, R=0, G=128, B=0, argb=-16744448
+libgdiplus: a=255.000000, r=0.000000, g=128.000000, b=0.000000
+I also did a test with Color.Green on the Microsoft Framework. The ARGB value is exactly 
+the same as in Mono.
+BTW with the latest libgdiplus version, the bmp.Save() methods throws an exception now. 
+But this seems totally unrelated. I first want to test some other things before submitting a 
+bug here.