[Mono-bugs] [Bug 77416][Maj] Changed - Forms Layout Problems

[bugzilla-daemon at bugzilla.ximian.com]

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 at novonyx.com.

http://bugzilla.ximian.com/show_bug.cgi?id=77416

--- shadow/77416	2006-01-31 09:38:33.000000000 -0500
+++ shadow/77416.tmp.26944	2006-02-02 20:55:20.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 77416
 Product: Mono: Class Libraries
 Version: 1.0
-OS: 
+OS: unknown
 OS Details: Windows XP SP2
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Major
 Component: Windows.Forms
 AssignedTo: peter at novonyx.com                            
 ReportedBy: don at edvalson.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -61,6 +61,31 @@
 Additional Information:
 
 ------- Additional Comments From don at edvalson.net  2006-01-31 09:38 -------
 Created an attachment (id=16429)
 test app with screen shots to demonstrate layout problems (zip)
 
+
+------- Additional Comments From peter at novonyx.com  2006-02-02 20:55 -------
+Issue 1 is already fixed, and Issue 4 is not an a bug, as shown by 
+running the app on MS.Net. In the project it's marked as application 
+icon, which means if you look at it in, say, explorer on win32, you 
+will see the icon for the application. 
+To use the icon for the actual app when it's running you need to 
+first set the properties for App.ico to "EmbedResource", then you can 
+do the following in your InitializeComponent method: 
+this.Icon =  new Icon(GetType().Assembly.GetManifestResourceStream
+("WindowsApplication2.App.ico"));
+
+After that the application will use the icon in your vs.net project.
+
+To use it via Makefile on mono, add this to your mcs arguments:
+/resource:App.ico,WindowsApplication2.App.ico
+
+
+Both item 2 and 3 are related to the AutoScaling 'feature' of 
+WinForms. If you turn off scaling (by setting the MONO_MWF_SCALING 
+variable to 'disable') it will look as expected.
+
+I'm not yet sure if this is a bug or just related to differences in 
+font heights, I will update the bug again later.
+