Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Visual Basic 2008 Programmer's Reference ISBN: 978-0-470-18262-8
This is the forum to discuss the Wrox book Visual Basic 2008 Programmer's Reference by Rod Stephens; ISBN: 9780470182628
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Visual Basic 2008 Programmer's Reference ISBN: 978-0-470-18262-8 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Display Modes
  #1 (permalink)  
Old August 7th, 2011, 12:18 PM
Registered User
 
Join Date: Sep 2009
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Question To MDI or not to MDI

Quote:
Originally Posted by Rod Stephens View Post
(As an aside, Microsoft seems to provide less support for MDI forms with each release. I don't think their heart is really in MDI.)
Hi Rod, that "aside" (from a VB2010 thread) sorta caught my attention, as I am now attempting to create my first mdi-form app ever. The first question that came to mind was, of course, should I bother learning it? And secondly, if not, then what's would replace that?

What I had done in the past was to have individual forms hiding/showing based on needs, but that makes for a very messy environment. Would you say MDI is still the way to go?

thanks!

Real
Reply With Quote
  #2 (permalink)  
Old August 7th, 2011, 01:27 PM
Rod Stephens's Avatar
Wrox Author
Points: 2,999, Level: 22
Points: 2,999, Level: 22 Points: 2,999, Level: 22 Points: 2,999, Level: 22
Activity: 25%
Activity: 25% Activity: 25% Activity: 25%
 
Join Date: Jan 2006
Location: , , .
Posts: 601
Thanks: 1
Thanked 84 Times in 83 Posts
Default

I think it depends on your application. If it makes sense to you to use MDI, I would go ahead. The places where it doesn't seem to work as well any more are mostly in the way menus are merged. (It's been a while since I've looked at this so I don't remember everything it was doing.)

You may want to write some extra code to adjust menus and toolbars yourself if you can't live with the default behavior, but you can still have child forms inside the MDI parent form and that's quite useful for some applications.

In general, Microsoft seems more enamored of the browser-style application where you use hyperlinks and forward and backward buttons to navigate instead of using separate windows. I think they took the wrong lesson from the fact that users like to use browsers. I think the real reasons are that things like they are platform independent, provide large scrolling areas for reading text, provide hyper links, etc. That's all wonderful but doesn't make sense for some types of applications, particularly on the desktop.
__________________
Rod

Rod Stephens, Microsoft MVP

Essential Algorithms: A Practical Approach to Computer Algorithms

(Please post reviews at Amazon or wherever you shop!)
Reply With Quote
  #3 (permalink)  
Old August 7th, 2011, 02:19 PM
Registered User
 
Join Date: Sep 2009
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I totally see your point. And I suppose, if I was writing an internet application (browser, possibly email client, etc) that might make sense to go the hyperlink way. I can appreciate the use of forward/back buttons on a desktop application if it's in a wizard scenario (where information is logically entered in a particular sequence), but for independent chunks of information being displayed, MDI does seem to be the proper way to do it. So that's what's I've been poking at all morning, and so far so good. (I used your Wizard example from chapter 10 as a starting point).

Thanks for the help and valuable opinions you provide to the community!!

Real
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Displaying MDI Child Form Menus with MDI Parent ashu_from_india Pro VB 6 3 June 10th, 2008 11:01 PM
MDI & MDI Child Forms Menu's in VB2005 yulyos Visual Studio 2005 0 September 7th, 2007 09:49 AM
Controlling MDI child form from MDI parent panel LuxCoder VB.NET 2002/2003 Basics 7 April 11th, 2007 02:38 PM
Controlling MDI child form from MDI parent panel LuxCoder VB How-To 1 April 9th, 2007 03:25 PM
Controlling MDI child form from MDI parent panel LuxCoder Visual Basic 2005 Basics 2 April 9th, 2007 03:24 PM



All times are GMT -4. The time now is 01:33 AM.


Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.