<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I filed bug <a
href="https://bugs.kde.org/show_bug.cgi?id=409089"><b>409089</b></a>.
The docs do need updating also, in that they describe the tabs in
the Payees view.<br>
</p>
<div class="moz-cite-prefix">On 6/23/19 1:01 PM, Thomas Baumgart
wrote:<br>
</div>
<blockquote type="cite" cite="mid:9718108.mqlI4S8knX@thb-nb">
<pre class="moz-quote-pre" wrap="">On Sonntag, 23. Juni 2019 18:24:16 CEST Jack wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 2019.06.23 12:16, Brendan Coupe wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Thomas,
Let me know if you have a patch for me to test. I can easily add it
with my build scripts.
Jack, do you have a default category for the payee that sometimes has
multiple categories and sometimes (most times) does not? I assume
that setting a default category for a payee takes precedence. If the
transactions with one category has different categories each time
then I'm guessing that's an edge case that will be hard to handle
every time.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Ah - I did NOT have a default category set for that payee. I have just
set it to the most common use, and I will keep an eye out to see if
that seems to solve my problem. Thanks for the suggestion.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Your question about account versus category points out what I think
is an error in the user interface. I used the Payee tab label
"Default Account" in my email but the tab should probably be labeled
"Default Category" since that's what it really is.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
The underlying "problem" is that internally to KMM, categories ARE
accounts. I think that is mentioned in the handbook, but it is
certainly a frequent source of confusion. I agree it would be good to
change the tab label from "account" to "category." Thomas - should I
open a wishlist so we don't lose this?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I agree with this change. Do we need to update the docs for that change? Opening a bug on the tracker is a brilliant idea. This way we can track it and it will be mentioned in the release notes (most automatically). I am tempted to work on it soon, so it would be cool if you can check the documentation if it needs change and mention the result of the check in the bug entry.
</pre>
</blockquote>
</body>
</html>