Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 15 total
Thread TFrame vs MDI
Sun, Oct 7 2007 3:34 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Its been suggested that I should use TFrames rather than MDI for an app. Anyone care to share reasons why (or why not)? Is TFrame better for resource usage, more stable or.......

Roy Lambert
Mon, Oct 8 2007 11:43 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< Its been suggested that I should use TFrames rather than MDI for an app.
Anyone care to share reasons why (or why not)? Is TFrame better for resource
usage, more stable or....... >>

One thing that we're using now with the upcoming EDB Manager is normal forms
manually docked into a TPageControl. It works quite well and provides an
easy way to switch between the various open forms.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Oct 8 2007 1:51 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

>One thing that we're using now with the upcoming EDB Manager is normal forms
>manually docked into a TPageControl. It works quite well and provides an
>easy way to switch between the various open forms.

Interesting - so come on and issue the new version Smiley

Roy Lambert
Mon, Oct 8 2007 6:20 PMPermanent Link

"Adam H."
> << Its been suggested that I should use TFrames rather than MDI for an
> app. Anyone care to share reasons why (or why not)? Is TFrame better for
> resource usage, more stable or....... >>
>
> One thing that we're using now with the upcoming EDB Manager is normal
> forms manually docked into a TPageControl. It works quite well and
> provides an easy way to switch between the various open forms.

I too used to use MDI forms in my applications until I was advised against
it. (Personally, I thought that MDI would have been great for more than what
it was designed for, but alas - I guess that wasn't to be).

I now have a couple of applications also using normal forms docked onto
Tabsheets / Page Controls. Took a little bit of getting used to (as some
events like OnActivate don't fire for the form when you expect them to), but
with the help of inherited forms and some other traps elsewhere in my code,
I was able to get around this.

It now works quite well, and I no longer have to worry about the limits of
MDI. (Putting them on a page control still allows my users to switch between
open forms in my application).

Cheers

Adam.
Mon, Oct 8 2007 6:40 PMPermanent Link

"Darren Davis"
"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:C1CDCE70-BF66-4F5A-B2B6-C5D701C6CDA6@news.elevatesoft.com...
>
> Interesting - so come on and issue the new version Smiley
>
> Roy Lambert
>

Have a peak here: http://www.delphiness.com/articles.htm
Notably article 3 - might be of interest?
D.

Tue, Oct 9 2007 2:56 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Adam


>I too used to use MDI forms in my applications until I was advised against
>it.

This is my sticking point - I've been advised to use frames rather than MDI but that's it - no justification, no reason, the best I've been able to find is M$ says MDI is a bad thing - and we all totally believe M$ don't we Smiley

Roy Lambert
Tue, Oct 9 2007 4:07 AMPermanent Link

"Adam H."
Hi Roy,

>>I too used to use MDI forms in my applications until I was advised against
>>it.
>
> This is my sticking point - I've been advised to use frames rather than
> MDI but that's it - no justification, no reason, the best I've been able
> to find is M$ says MDI is a bad thing - and we all totally believe M$
> don't we Smiley

Absolutely - and that's the main reason I rushed straight into .Nyet.  Smile

Boy - I'm glad I didn't port my projects to .net - I'd be kicking myself
atm.

I wish I could remember the reasons why, but I can't off the top of my head.
(Will let you know if I do), but from what I recall, I was having a number
of issues with MDI forms in my application, and pretty much the responses
were that MDI forms were designed for a particular environment only, and
enhancements (or bug fixes) to MDI were not going to be forthcomming, so the
issues I had then were never going to be fixed. Thus being the case,
embedded forms became the best option for me anyway.

IIRC, these issues weren't going to be show stoppers, but being told that
bugs are never going to be fixed scares me. SmileyI don't think it was a
"Delphi" issue, as much as a Microsoft MDI issue.

'Tis a pitty though. I believe that MDI (or at least MDI like) forms are a
great way to develop, and wish that they were taken more seriously.

If you're not having any issues with MDI forms, and they're working
perfectly for you, I wouldn't be in any rush to move, but if you do have a
few issues - from what I was told, they'll never be fixed.

Cheers

Adam.
Fri, Oct 12 2007 11:32 AMPermanent Link

Chris Erdal
Roy Lambert <roy.lambert@skynet.co.uk> wrote in
news:7208B552-1EAA-4D35-9DFF-86C136FE9C1E@news.elevatesoft.com:

> Its been suggested that I should use TFrames rather than MDI for an
> app. Anyone care to share reasons why (or why not)? Is TFrame better
> for resource usage, more stable or.......

Roy,

 I used TFrames for a short while in D5, and threw them out in despair
after ALMOST getting them to work as expected for the umpteenth time.

I seem to recall that my main problem was trying to inherit forms with
Tframes on them, and also using the same frame multiple times on the same
form. I think that one was a frame allowing users to switch money edits
from Francs to Euros without altering the underlying data - things got
mixed up between frames, and I couldn't work out how to avoid it - much
worse than AdvStringGrid Wink

Like Tim, I'm now well into inserting normal forms onto panels, and I've
no problems with that at all, which was rather a surprise.

I register all my forms in the dpr, and all except the Mainform and the
Datamodule are created dynamically when needed and released when not.

No forms need to "use" any others, and all can drop any other onto a
panel at the click of a TJvTabControl. As soon as they're there, each
knows about the other and can set up master/detail relationships if
required, to as many levels of forms-in-forms-in-forms as seems
reasonable.

Good luck!

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.25 build 4 + EDB 1.04 build 3)

Fri, Oct 12 2007 1:26 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Chris


You're the second person that's brought up a problem with inheritance.

On the other hand no-one has yet been able to tell me what's so evil about MDI Smiley


Roy Lambert
Sun, Oct 14 2007 8:53 AMPermanent Link

Chris Erdal
Roy Lambert <roy.lambert@skynet.co.uk> wrote in
news:CBF38979-4CFB-47B7-A251-2E9510E5CFF7@news.elevatesoft.com:

> On the other hand no-one has yet been able to tell me what's so evil
> about MDI Smiley
>

Not surprising - it's ideal for some applications, imho.

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.25 build 4 + EDB 1.04 build 3)

Page 1 of 2Next Page
Jump to Page:  1 2
Image