| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
already.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
totals column of both the register and balance reports. This is different
from the internal calculated total, which is still "total_expr".
|
|
|
|
| |
commodity_t::exchange.
|
| |
|
| |
|
| |
|
|
|
|
| |
value_t objects.
|
| |
|
|
|
|
| |
COMMODITY_WALKED, for avoiding infinite recursions during price lookups.
|
|
|
|
|
|
| |
makes it possible to find all possible prices for a commodity by walking the
map of pricing relationships to all other commodities, even if the relation is
distant.
|
|
|
|
| |
specific commodity.
|
|
|
|
| |
mappings.
|
| |
|
| |
|
| |
|
|
|
|
| |
entry only if it is "more" cleared.
|
|
|
|
| |
testing!
|
|
|
|
| |
unit tests. 6 was good enough.
|
| |
|
|
|
|
|
| |
be handled differently, since paying attention to places after the decimal is
not enough.
|
|
|
|
| |
when a match is found.
|
|
|
|
| |
item_t (which it also is).
|
| |
|
|
|
|
| |
find_price does not work yet.
|
|
|
|
| |
valuation changes.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
price (based on the cost of the transactions), don't automatically use the
date and the entry code -- since most people aren't going to be that specific
at the time of sale, it's causes confusion in certain cases.
|
| |
|
| |
|
| |
|