One approach to complex screens with tabs is to break it up into different
forms and have the forms dyanamically created and destroyed behind events
triggered by the pagecontrol/tab component. To do this you create the form,
and them make its parent the tabsheet. You also need to set the form
properties - to align client etc so it displays correctly etc.
The advantage of this is that you can reuse the forms in other areas of the
application. In other words you can build forms which are designed to be
plonked onto other forms. It will also considerably ease the resources
needed for that form - which is why I mention it.
As for resources, unless you are dyanamically generating objects and not
freeing them or breaking the application mid flow as previously mentioned
there should be no memory problems.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 18, 1999 11:09 AM
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: System Resources
>
> Bugs ? in my program ?? :)
>
> Unfortunately I have the low resources situation I described the very
> first time I run my app. I do have one form with many tabs and a large
> number of controls which may be the culprit. Otherwise, yes, I'd expect to
> slowly run out of resources over time running/debugging my app as you do.
> Basically I have to close a few units so delphi is consuming less
> resources before running my app (plus kill off background processes like
> backup schedulers etc).
>
> Where in windows do limits of available handles etc get set ? surely the
> number of concurrently allocated handles is related to the available
> memory, so increasing my memory should have helped ?
>
> -----Original Message-----
> From: Myles Penlington [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, August 18, 1999 10:10 AM
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: System Resources
>
> If you Break/Reset your program from within D3, it does not
> cleanup/release
> all the system resources eg I presume these are things like window
> handles,
> file handles, memory.
>
> The other thing is bugs that do not release objects created in your
> program
> etc.
>
> I get this after running a while and have done a few Ctrl-F2, and
> just
> normally close D3 and re-open.
> Myles.
>
> > -----Original Message-----
> > From: Andrew Masters [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, August 18, 1999 9:52 AM
> > To: Multiple recipients of list delphi
> > Subject: [DUG]: System Resources
> >
> > Hi,
> >
> > I originally sent this off topic but it didn't get posted for some
> reason
> > (is the off topic list working ?), so....
> >
> > My development pc runs out of system resources (and eventually
> hangs) when
> > I have my project open with D3 and then run it from within D3. I
> tend to
> > have a lot of units open concurrently. It has got progressively
> worse as
> > my project has grown so I assumed my pitiful 32MB RAM was a factor
> and so
> > bumped it up to 80MB (all installed OK etc). This had no effect on
> my
> > system resources ?? What "resource" am I running out of ?? Anyone
> have
> > similiar problems ? ideas ?
> >
> > FYI, using D3, Win95. Issues like swap file space are OK.
> >
> > TIA
> > Andrew Masters
> > Clinical Solutions Ltd
> > Auckland, NZ
> > Ph: +64-9-476-0106
> > Fax: +64-9-476-0108
> > e: [EMAIL PROTECTED]
> >
> >
> --------------------------------------------------------------------------
> > -
> > New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> > Website: http://www.delphi.org.nz
>
> --------------------------------------------------------------------------
> -
> New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
