[Mono-bugs] [Bug 82767][Min] Changed - MDI Form: Win32 when maximized adding new child causes unmaximize inconsistency

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Sep 10 15:51:13 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 andyhume32 at yahoo.co.uk.


--- shadow/82767	2007-09-09 11:24:20.000000000 -0400
+++ shadow/82767.tmp.5832	2007-09-10 15:51:13.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 82767
 Product: Mono: Class Libraries
 Version: 1.2
+OS: unknown
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Minor
 Component: Windows.Forms
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: andyhume32 at yahoo.co.uk               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -46,6 +46,19 @@
 in child and in MDI menu!
 Mono Suse VM: See top-most child full size, and with its maximize control 
 icon set!
 6. Hit Maximize control icon.
 Both: arranges in a new cascade (bad--two windows at top left), and 
 control icons now as expected.
+------- Additional Comments From andyhume32 at yahoo.co.uk  2007-09-10 15:51 -------
+There is another issue that occurs when the current child status is 
+maximized.  The case is when a Cascade or Tile H/V operation is 
+selected then -- the maximize state again remains, but in this case 
+it should have been cleared.
+What we expect is that when the Cascase or Tile operation is carried 
+out, that the maximized state should be cleared and the child 
+windows arranged as suits the operation.
+On Mono one sees the same inconsistent maximized state as for the 
+main report.

More information about the mono-bugs mailing list