Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Multiple-document interface
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Disadvantages=== * Without an MDI frame window, floating toolbars from one application can clutter the workspace of other applications, potentially confusing users with the jumble of interfaces. * Can be tricky to implement on desktops using multiple monitors as the parent window may need to span two or more monitors, hiding sections. * [[Virtual desktop]]s cannot be spanned by children of the MDI. However, in some cases, this is solvable by initiating another parent window; this is the case in [[Opera (web browser)|Opera]] and [[Google Chrome|Chrome]], for example, which allows tabs/child windows to be dragged outside of the parent window to start their own parent window. In other cases, each child window is also a parent window, forming a new, "virtual" MDI [https://web.archive.org/web/20110818050252/http://hypotext.webs.com/web1.htm]. * MDI can make it more difficult to work with several applications at once, by restricting the ways in which windows from multiple applications can be arranged together without obscuring each other. * The shared menu might change, which may cause confusion to some users. <!-- But if this is a common problem, why is it not a problem on OS X, where the menu bar is shared by ''all'' applications? Can someone actually cite studies on this subject? ( I agree to this comment --~~~~ ) --> * MDI child windows behave differently from those in [[single-document interface]] applications, requiring users to learn two subtly different windowing concepts. Similarly, the MDI parent window behaves like the desktop in many respects, but has enough differences to confuse some users. * Deeply nested, branching hierarchies of child windows can be confusing. * Many window managers have built-in support for manipulating groups of separate windows, which is typically more flexible than MDI in that windows can be grouped and ungrouped arbitrarily. A typical policy is to group automatically windows that belong to the same application. This arguably makes MDI redundant by providing a solution to the same problem. * Controls and hotkeys learned for the MDI application may not apply to others, whereas with an advanced Window Manager, more behavior and user preference settings are shared across client applications on the same system
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)