[Mono-bugs] [Bug 65777][Min] Changed - Some Windows.Forms bug
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 20 Sep 2004 02:55:46 -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 peter@novonyx.com.
http://bugzilla.ximian.com/show_bug.cgi?id=65777
--- shadow/65777 2004-09-20 02:33:32.000000000 -0400
+++ shadow/65777.tmp.24631 2004-09-20 02:55:46.000000000 -0400
@@ -1,12 +1,12 @@
Bug#: 65777
Product: Mono: Class Libraries
Version: unspecified
OS: Windows XP
OS Details: Win2k Mono 1.0.1
-Status: NEW
+Status: ASSIGNED
Resolution:
Severity: Unknown
Priority: Minor
Component: Windows.Forms
AssignedTo: mono-bugs@ximian.com
ReportedBy: tgraupmann@yahoo.com
@@ -91,6 +91,37 @@
Email me at tgraupmann@yahoo.com if this doesn't make sense to you.
------- Additional Comments From martin@ximian.com 2004-09-20 02:33 -------
This is clearly not a debugger bug.
Let's have the Windows.Forms guys deal with it, or close it, or do
whatever.
+
+------- Additional Comments From peter@novonyx.com 2004-09-20 02:55 -------
+This is most likely due to a mismatch between the version of cairo
+being used and the version of gdi+ being used. I posted a patch to
+the winforms mailing list on the the 13th of september. Here's the
+link: http://lists.ximian.com/archives/public/mono-winforms-list/2004-
+September/000880.html
+
+and here the patch:
+Index: gdip.h
+===================================================================
+RCS file: /cvs/public/libgdiplus/src/gdip.h,v
+retrieving revision 1.92
+diff -u -r1.92 gdip.h
+--- gdip.h 26 Jul 2004 07:32:59 -0000 1.92
++++ gdip.h 13 Sep 2004 17:20:35 -0000
+@@ -74,7 +74,7 @@
+struct cairo_font {
+ int refcount;
+ cairo_matrix_t matrix;
+- //void *glyph_cache;
++ void *glyph_cache;
+ const struct cairo_font_backend *backend;
+};
+
+That should resolve the issue.
+
+Be aware that winforms is a) alpha and b) being rewritten fully
+managed. Check the winforms archive for more information.
+
+Please close this bug if the patch resolves your issue.