| Summary: | Show warning frame around category only when leaving category widget | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | tnemeth |
| Component: | ux-ui | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
tnemeth
2025-11-29 11:25:56 UTC
Are you sure you did not enter an amount in either credit or debit? Only if that is not equal to zero the red dotted line will be displayed. A tooltip should tell you the reason (missing category assignment). (In reply to Thomas Baumgart from comment #1) > Are you sure you did not enter an amount in either credit or debit? Only if > that is not equal to zero the red dotted line will be displayed. A tooltip > should tell you the reason (missing category assignment). You are right: it's when I entered a debit amount, then moved, using tab, to the next field which was the credit amount. Whatever: why a category should be mandatory and if so, marked in red at this point in time. If you really need the category to be mandatory, then mark it in red _after_ passing through the field with no input :) > Whatever: why a category should be mandatory and if so, marked in red
> at this point in time. If you really need the category to be mandatory, then
> mark it in red _after_ passing through the field with no input :)
KMyMoney shows a dashed line to catch the users attention (which apparently has worked). A category assignment is not strictly necessary but leads to false reporting. This is what double-entry accounting is all about.
I understand your wish to postpone the display of the red frame. This is a bit more complex in cases where the tab order has been modified. Therefore, I turn this into a wish list item and adjust the title.
|