MDI Interface

Now you're talking about Google playing catch-up with HeidiSQL... Will you consider issue #513 for version 4.0? I believe it's one of the biggest usability issues for HeidiSQL newbies.

If you're ok with waiting some further months for the 4.0 - yes :)

To be honest, we should put out the release very soon, but this feature is uncritical in my eyes. Although it seems worth a look soon when most other bugs are fixed.

I suspect it's one of those requests than sound trivial to the profane but are really hard to implement...

Perhaps you could just hide or disable the inner window controls :-? Given that you don't need to implement a Unicode TControlDisabler or something weirder.

If you're ok with waiting some further months for the 4.0 - yes :)

To be honest, we should put out the release very soon, but this feature is uncritical in my eyes. Although it seems worth a look soon when most other bugs are fixed.

I too would love to see this in action! Maybe something like Google did with Chromewould be nice to see it maybe at least started then the community can have a voice on it :)

The wait is no problem if it will be used :)

Wish I had found this thread before I added a new item to the tracker -- sigh... I searched, I did, but didn't know to refer to it as MDI.

My issue is that I like the MDI, and like having multiple connection windows in the same parent window.

Can somebody explain why the MDI is being removed (and why, if it is being removed, the parent/child window thing was left, why not just have the dialog create an all in one window?

Was discussd longer time ago, dunno exactly each reason. Main thing was that MDI itself is legacy stuff and Windows allows taskbar grouping.

Anse correctly mentions that MDI is legacy. And has been for a long time.

(M)ultiple (D)ocument (I)nterface was appropriate in the early days of windows, where resources were scarce and users were newbies.

It essentially allowed an application to *sort of* create its own "desktop" with multiple child windows confined to the window area of the parent but which could be minimized maximized or tiled whatever.

A few things happened... Screens got bigger, programs got better, and MS realized that the MDI API was a piece of junk that was trying to mimick the rest of the OS.

So MS junked MDI for MS Office and declared MDI dead. Thats when you saw every document in MS Office get its own parent window with no MDI container.

There is nothing to like about MDI, it was hard to program, and difficult to use for users... Let it go "gracefully"..."Havent we done enough?"

In my opinion, it's okay if HeidiSQL keeps each session in a separate window. It's not very common to be connected to more than two servers at the same time. But I don't think everybody hates MDI interfaces*. Just look at what happened when web browsers grew up tabs, everybody was so excited. And I'd never use a non-tabbed text editor for serious work. The problem is poorly designed MDI interfaces, not the idea of MDI itself.

Can somebody explain why the MDI is being removed (and why, if it is being removed, the parent/child window thing was left, why not just have the dialog create an all in one window?

Now the case - the MDI mechanism has been completely removed recently and there is only one main window left.