[Mono-bugs] [Bug 80663][Wis] Changed - MDI + MenuStrip problems in 1.2.3

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

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

--- shadow/80663	2007-01-29 19:03:05.000000000 -0500
+++ shadow/80663.tmp.15870	2007-01-30 13:42:04.000000000 -0500
@@ -1,17 +1,17 @@
 Bug#: 80663
 Product: Mono: Class Libraries
 Version: 1.0
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: Windows.Forms
-AssignedTo: toshok at ximian.com                            
+AssignedTo: monkey at jpobst.com                            
 ReportedBy: trofimich at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
 Summary: MDI + MenuStrip problems in 1.2.3
@@ -37,6 +37,20 @@
 
 
 ------- Additional Comments From trofimich at gmail.com  2007-01-29 19:03 -------
 Created an attachment (id=18580)
 Child maximizing bugs
 
+
+------- Additional Comments From monkey at jpobst.com  2007-01-30 13:42 -------
+I cannot reproduce #1.  It is most likely an issue caused by doing
+things in a different order than I thought of.  I have attached the
+test case I use that works.  Can you please post a sample that will
+crash as well as the stacktrace?
+
+As for the other 2, merging has not been implemented in MenuStrip, and
+probably is pretty far down on the list.  I had thought that would be
+obvious because if anyone tried to use AllowMerge, they would get an
+error since it does not exist in mono.  According to MSDN docs, this
+defaults to false, but apparently it really defaults to true, so I can
+see now how people would expect it to work without setting AllowMerge.
+ That is unfortunate.