Re: Problem freeing components with .free

TeChNoInSiDe wrote:
First, thanks for your answer. The example I explained on last
message is the base of my program. But the program itself is a little
more complex. Let me explain:

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.

It's just the "save images" button that's giving you trouble, isn't it? Keeping that button around isn't going to have any significant effect on your program's resource usage.

Go ahead and close all the image windows, but keep that one button.

--
Rob
.

Quantcast