Click here to Skip to main content
15,892,746 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
As in REMOVE not DISABLE.
Thanks!
Posted
Comments
Sergey Alexandrovich Kryukov 7-Mar-14 1:36am    
Why? What's wrong with maximizing? Sounds like a bad idea.
But even worse idea is using MDI...
—SA

Have a look here: Remove Min/Max Buttons From MDI Form[^]
But... i'm fully appreciating Sergey's answer.
 
Share this answer
 
Here is the idea: who needs MDI, ever? Why torturing yourself and scaring off your users?
Do yourself a great favor: do not use MDI at all. You can do much easier to implement design without it, with much better quality. MDI is highly discouraged even by Microsoft, in fact, Microsoft dropped it out of WPF and will hardly support it. More importantly, you will scare off all your users if you use MDI. Just don't. Please see:
http://en.wikipedia.org/wiki/Multiple_document_interface#Disadvantages[^],
How to Create MDI Parent Window in WPF?[^].

I can explain what to do instead. Please see my past answers:
How to Create MDI Parent Window in WPF? [Solution 2],
Question on using MDI windows in WPF[^],
MDIContainer giving error[^],
How to set child forms maximized, last childform minimized[^].

—SA
 
Share this answer
 
Comments
Maciej Los 7-Mar-14 2:44am    
Never ending story...
+5!
Sergey Alexandrovich Kryukov 7-Mar-14 8:48am    
Thank you, Maciej.
—SA

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900