All you need to do is mark the time at which an account was last
saved. Next time you load it into GnuCash, it processes all the
'timed' transactions that occurred between then and "now". You really
don't need (or want) asynchronous events here. "Cron" and "at" are
superfluous. It's not like we need GnuCash to start up on its own and
tell us a bill is due. ;)
I hope we're not over-engineering a solution to what (to me) is a set
of simple problems: Installment Loans and Depreciation.
-derek
Rob Browning <[EMAIL PROTECTED]> writes:
> It depends on how you want to think about the events. If you think of
> them as "going with" the data, then you'd store them inside the data
> file, but unless you're clever, that makes it harder to have the
> events be executed at arbitrary times regardless of whether or not
> gnucash is running. For that, the information (or at least triggers
> that know where the real information is) need to be stored with a
> server or something. I can imagine that being able to execute gnucash
> code at arbitrary times might be an important feature. For example
> imagine being able to schedule some "constraint" type events:
>
> (gnc:add-event '(every-n-days 1)
> (if (negative? (gnc:balance some-account))
> (send-emergency-message
> (string-append "Account " account-name " has a negative balance!"))))
>
> This is supposed to guarantee that you will get notified if you (or
> some of your other automatic actions) cause the super-important
> account to go negative on a given day.
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL N1NWH
[EMAIL PROTECTED] PGP key available
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
