Scheduled Transactions dead list

[Josh Sled]

On Fri, 2006-05-05 at 16:56 -0400, Andrew Duggan wrote:

> I think then I am on the right track, since that's what I did.  Plus I've 
> just gotten it to work - at least through a couple of rounds of initial 
> testing :-)  Now I can just look at the tool bar and see how many pending 
> txn/reminders I have, click the button and run them. :-)

Awesome. :)

> I had erroneously thought I should free the lists etc that I ended up 
> creating, but after digging a little deeper, (and my testing confirms this) 
> that I should not do that, since the sxlist (as QOF collection gets stashed 
> in the book->hash_of_collections as GNC_ID_SXTT.  As we all know, "stuff" 
> don't like having its data structures de-allocated out from underneath it :-/

Yeah, the allocation rules for those objects are pretty implicit ...
definitely the SchedXactions themselves shouldn't be freed up, but all
the {toCreateTuple}s and {toCreateInstances}s and {reminderTuple}s and
such should be.  The freeing functions as implemented in
dialog-sxsincelast.c (e.g. gnc_sxsld_free_toCreateTuple_list) should do
(most of) the right thing.  I'm pretty sure the dialog is leaky at
present. :/

-- 
...jsled
http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo ${a}@${b}`