Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Numeric input as confirmation of account suggestion #76

Open
allgreed opened this issue Jun 23, 2023 · 1 comment
Open

Numeric input as confirmation of account suggestion #76

allgreed opened this issue Jun 23, 2023 · 1 comment

Comments

@allgreed
Copy link

I still haven't got rid of this intuition after a year+ of using hledger-iadd so it might be worth considering.

Currently it's required to enter both the account and the amount as 2 separate steps.

I keep doing the following thing while entering a transaction:

  1. I accept the date
  2. I enter the description
  3. I type the amount and press enter
    Then I have the amount suggested as a new account and have to back up and enter the data properly.

Would it make sense to interpret input that stars with a digit on an account question as "yes, I like the suggested account name, here's the amount"? Note: if yes - a flag might be a good idea since it's perfectly possible for someone to have accounts that begin with a number

@hpdeifel
Copy link
Owner

I also do this from time to time, so there certainly is a bit of a UX problem. However, I'm not entirely sold on the suggested workaround.

I think the the current UI in general isn't great at communicating the current state of your q&a session. For example, I also sometimes try to type a description into the date prompt or an account name into the description field. In general, you either have to have perfect muscle memory or interpret a few spread-out clues and read text to know where you are.

A better way of presenting the current state, e.g in a WYSIWYG fashion like an HTML form or similar, would probably(hopefully) go along way to eliminate these sort of errors. However, that's of course a lot of work and might create new problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants