https://bugs.kde.org/show_bug.cgi?id=314955
Bug ID: 314955
Summary: Ledger 'Enter' button enabled prematurely, and other
strangenesses
Classification: Unclassified
Product: kmymoney4
Version: git master
Platform: Other
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kmymoney-devel@kde.org
Reporter: agande...@gmail.com
Normally, I do not use the Transaction Form, but today I did, and noticed a
difference in behaviour compared to direct transaction entry.
Previously, I had noticed that it was possible to enter just an amount, and
immediately the Enter button became enabled. I thought it was a bit odd, but
just accepted it as not harmful. Today, however, when using the transaction
form, the Enter button did not then become enabled.
So, I poked about a bit.
When not using, or when using, the transaction form -
1a) Enter a payee. That's OK.
1b) Now enter a single character in the memo. Enter enabled.
2a) Enter a memo character. That's OK.
2b) Now enter a payee. That's still OK.
2c) Now enter another memo character. Enter enabled.
3a) Enter an account. Enter enabled.
4a) Enter a tag. Enter enabled.
So, apart from the amount field, the two methods seem similar.
Investment entry seems OK.
Reproducible: Always
Steps to Reproduce:
1. as above.
2.
3.
Actual Results:
as above.
Expected Results:
The two entry methods should behave similarly, so far as the amount field is
concerned.
A payee and a memo don't seem to be sufficient data for a transaction to be
accepted.
I wouldn't expect it to be valid to be able to enter a transaction without its
quota of fields, although there may be a valid reason to be able to do that.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
