Re: Problem freeing components with .free
- From: Hans-Peter Diettrich <DrDiettrich1@xxxxxxx>
- Date: Thu, 15 Feb 2007 03:27:56 +0100
TeChNoInSiDe wrote:
User can open any quantity of image folders, and all components are
created dynamically. In the case, if user choose to save all image of
one specific folder, then I need to destroy them and reposition other
folders and images. In fact I can set only visibility, but because of
high volume of folders being treated at same time, I think some old
computers on my office would crash if i don't clear unnecessary
memory, not to talk about other modifications i'll need to make, where
the timer would be more helpful.
No system will crash due to a lack of RAM. Virtual memory is in use since Win 3.0.
I was just wondering if there is no trick or workaround to get rid of
this problem!
OH on TComponent.Owner property:
Indicates the component that is responsible for streaming and freeing this component.
IMO this should work for you, instead of X.Free:
X.Owner.RemoveComponent(X);
DoDi
.
- Follow-Ups:
- Re: Problem freeing components with .free
- From: J French
- Re: Problem freeing components with .free
- References:
- Problem freeing components with .free
- From: TeChNoInSiDe
- Re: Problem freeing components with .free
- From: Sebastian Doht
- Re: Problem freeing components with .free
- From: TeChNoInSiDe
- Problem freeing components with .free
- Prev by Date: Re: TaskBar flash and progress display, and fsStayOnTop
- Next by Date: Re: The Zen nature of a Delphi database application
- Previous by thread: Re: Problem freeing components with .free
- Next by thread: Re: Problem freeing components with .free
- Index(es):
Relevant Pages
|