[Mono-bugs] [Bug 81144][Min] Changed - [X11] Incorrect PrimaryScreen.Bounds returned on X11

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Mar 14 18:49:06 EDT 2007


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 monkey at jpobst.com.

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

--- shadow/81144	2007-03-14 16:57:43.000000000 -0500
+++ shadow/81144.tmp.5307	2007-03-14 17:49:06.000000000 -0500
@@ -2,22 +2,22 @@
 Product: Mono: Class Libraries
 Version: 1.2
 OS: GNU/Linux [Other]
 OS Details: Debian 4.0 x86
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Minor
 Component: Windows.Forms
 AssignedTo: toshok at ximian.com                            
 ReportedBy: gehossafats at netmdc.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Bounds discrepency between Linux and Windows
+Summary: [X11] Incorrect PrimaryScreen.Bounds returned on X11
 
 Description of Problem:  System.Windows.Forms.Screen.PrimaryScreen.Bounds
 return incorrect value on Linux (Debian 4.0, kde 3.5 x86 (AMDk7))  
 
 
 Steps to reproduce the problem:
@@ -52,6 +52,9 @@
 
 There is not any documentation at present for Windows.Forms on the Mono
 documentation web site.  Viewing the ms .net documentation, states that
 PrimaryScreen get the primary display and that Bounds get the bounds of the
 display.  WorkingArea gets the display minus taskbar, docked windows,
 docked toolbars.
+
+------- Additional Comments From monkey at jpobst.com  2007-03-14 17:49 -------
+Changed summary to reflect PrimaryScreen.Bounds instead of just Bounds.


More information about the mono-bugs mailing list