"Patrik Lermon" <[EMAIL PROTECTED]> writes:
>> Underlying assumptions in the business features that Invoices are always
>> on sign and Payments are always the other. A negative payment would
>> therefore look like an Invoice.. but it's NOT an invoice.. And it would
>> confuse the payment-merging processing for handling over/under-payments
>> across multiple invoices.
>>
>> Feel free to look at src/business/business-core/gncInvoice.c if you want
>> to try to come up with a better approach.
[snip]
> I think that assumption is actually wrong.
Oh, I'm not saying that the assumption is RIGHT, just that the
assumption was made and it exists in the code. What it means is that
it's not EASY to make this change. It's not just as simple as
removing the check in the UI. It's a deeper issue; the whole set of
algorithms need to be re-thunk in order to remove this assumption.
So, the challenge to you is to come up with a patch that does it!
Good Luck!
> /Patrik
-derek
--
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-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
