Alle 12:25, domenica 15 febbraio 2004, [EMAIL PROTECTED] ha scritto:
> > > I fixed this. The problem was that the behaviour of Borland's TList
> > changed
> > > - it got (a lot!) slower. In older TList implementations TList.Clear
> > didn't
> I understand their reasons, but it's not so cool if yo
On Fri, 13 Feb 2004, Charl van Jaarsveldt wrote:
> Hi all,
>
> According to the docs for TObjectList, if it's OwnsObjects property is
> set to true, then, if you clear the list, it will automatically call
> free for all the objects contained in the list. At least that is how I
> understand i
On Sat, 14 Feb 2004, Matt Emson wrote:
> > I fixed this. The problem was that the behaviour of Borland's TList
> changed
> > - it got (a lot!) slower. In older TList implementations TList.Clear
> didn't
> > do anything except free the memory for the list elements.
> > Now it calls Notification f
> I fixed this. The problem was that the behaviour of Borland's TList
changed
> - it got (a lot!) slower. In older TList implementations TList.Clear
didn't
> do anything except free the memory for the list elements.
> Now it calls Notification for all elements in the list, which is a time
> consumi
On Fri, 13 Feb 2004, Charl van Jaarsveldt wrote:
> Hi all,
>
> According to the docs for TObjectList, if it's OwnsObjects property is
> set to true, then, if you clear the list, it will automatically call
> free for all the objects contained in the list. At least that is how I
> understand i
Hi all,
According to the docs for TObjectList, if it's OwnsObjects property is
set to true, then, if you clear the list, it will automatically call
free for all the objects contained in the list. At least that is how I
understand it.
Now, I did a little test program and found that calling
TObj
