Gnucash 1.8.2 first impressions

Linas Vepstas linas at
Sat Apr 12 23:32:16 CDT 2003

On Sat, Apr 12, 2003 at 09:59:00PM -0400, Derek Atkins was heard to remark:
> linas at (Linas Vepstas) writes:
> > 1) they need to be linked/tracked appropriately:
> >    If user makes a typo in the register, then corrects it, the price in the 
> >    price db needs to be corrected as well: even if the correction is days 
> >    or weeks later.
> > 2) Have to be careful with math in the register:  due to round off errors,
> >    if we define price = value/amt, then one will find that value != price * amt.
> >    It was Quickens inability to correctly do this bit of math that got me started
> >    on Gnucash, oh, what six & a half years ago ... 
> > 
> > If 1) and especially 2) aren't implemented correctly, it will drive users up a 
> > wall.  This may be why register-prices don't go into the pricdedb; rob
> > decided to punt when he coded this.
> I actually think #1 is a harder problem...

Nahh, a few dozen lines of code at most; you use kvp to store 'pointers'
between the two objects, by storing thier guids :  

kvp_set_value (split->kvp, "/price-mate", gnc_price_get_guid (price));
etc. and its inverted link; and then xaccLookupEntity () of the 
guid fetched from out of kvp tree.

I've used this stunt elsehwere;  its probably generic enough that
we should write a generic utility to do it.

(The 'gemini' code is used to interlink clones of account trees with 
each other in this way).


pub  1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas at>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984  3F54 64A9 9A82 0104 5933

More information about the gnucash-devel mailing list