Jack, On Montag, 14. Januar 2019 00:22:56 CET Jack Ostroff wrote:
> I just filed a bug that the ledger, when displaying transactions for a > category, does not show the name of that category, but shows the name > of the most recent account for which the ledger was displayed. That is a known issue and not easy to fix, as the drop down box only contains accounts and no categories. Not sure, how to fix this. > The other thing I just rediscovered about the category ledger is that, > for me, a large number of these transactions are matched, but not yet > accepted. The matches WERE accepted in the actual account ledger which > shows that transaction. I have not yet looked into the XML file to see > why the match shows accepted from the perspective of the account, but > not of the category. A match always happens on a split basis and so does the acceptance. I've never seen any category in the matched state (showing in bold etc.). So how do you come to the conclusion that a "match shows accepted" in the ledger? > I'm just reporting here, in case it might reflect some problem with the > logic of accepting matched transactions, or of how that acceptance is > stored. The acceptance itself is not stored at all. The matched state is where a split contains a complete transaction as a member. This is the transaction it was matched against. Once you accept it, this contained transaction is simply discarded. We only store it to be able to 'unmatch' and bring that transaction back into the ledger. So from my perspective things look OK. -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp ------------------------------------------------------------- Windows 8 is truly the first Windows version made for the Internet era... I had to search the web to figure out how to reboot. -- Eike Hein (paraphrased) -------------------------------------------------------------
signature.asc
Description: This is a digitally signed message part.
