Bug 552329

Summary: MonoDevelop cannot be resized?
Product: [Mono] MonoDevelop Reporter: Jörg Battermann <jb>
Component: generalAssignee: Michael Hutchinson <mhutchinson>
Status: RESOLVED DUPLICATE QA Contact: MD Bugs <monodevelop-bugs>
Severity: Minor    
Priority: P5 - None    
Version: 2.2 Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: Mac OS X 10.6   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jörg Battermann 2009-11-03 23:02:08 UTC
Description of Problem:
Basically all I did was grab the 2.2 beta 2 & ran it.. and for some reason it's always in maximized mode and simply cannot be resized. I've created a short screencast showing the problem (which basically is just annoying rather than being a breaker) at uploaded it to vimeo at: http://vimeo.com/7423158

(please don't mind the demo note from the screencast app & the current wait time to convert it at vimeo is 30 minutes as of creating this bug report). Please make sure to either watch it in HD or download the .mov (available at this site at the very lower right corner)

Steps to reproduce the problem:
1. Start MonoDevelop 2.2 beta 2
2. Try to minimize it by clicking (& holding the mouse button) on the lower right corner


Actual Results:
Cursor changes to the typical resize icon, but dragging does not have any effect. Releasing the mouse button does not change back to the typical cursor of the mouse, plus as long as you stay within monodevelop, you cannot click any of the buttons etc. Only by clicking in the outer scope (e.g. the background/finder) or in the menubar the cursor changes to its old state and you can click the monodevelop buttons again. Trying the typical OS 'green plus' in the upper left corner of the app does not help or change this particular behavior.

Expected Results:
I should be able to resize the monodevelop window just like any other application

How often does this happen? 
Everytime

Additional Information:
Comment 1 Lluis Sanchez 2009-11-13 16:30:50 UTC
Isn't this already fixed?
Comment 2 Lluis Sanchez 2009-11-13 16:55:51 UTC
Dup.

*** This bug has been marked as a duplicate of bug 547670 ***