🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>> Is there a better way?
> 
> You already know a better way - use 'delete' instead.  There is
> nothing in your code that warrants the use of Release().


I do appreciate the help and the comments.
I was under the impression that the Release();  ProcessMessages() call 
actually fixed the problem as my code ran much much longer than it ever 
had before in this loop.

However, it does still occur.

With the straight 'delete' operator, my code lasts approximately 230 
cycles; with the Release(); ProcessMessages() operators instead of 
delete, the code goes nearly 800 cycles.  During each of these cycles 
are several hardware read/write commands, each dynamically creating and 
destroying that form; and with each cycle nearly 24k of memory is saved. 
  The data is stored in a TStringGrid.  Perhaps that is the real 
problem.  I don't quite see why since I can easily open a file and fill 
in a TStringGrid with 2x the amount of data collected during this loop 
and then dynamically create the dialog in question though. But I've been 
wrong before :)

As I said before the form in question is rather simple, and it has a 
TProgressBar, TLabel, and TButton on it; that's it.

I'm confused (1) why this is still happening, although basically Remy 
says I haven't done anything to fix the problem, which I can buy; 
however that brings me to my second confusion (2) why my code 
consistently runs much longer with the Release() than it did with just 
the delete.

Dan