mschieder@442: 
mschieder@442: 20180117 Magnus Schieder
mschieder@442: 
mschieder@442:   20170317 BER: Reproduce and then fix a defect that it is surprising which
mschieder@442:   entries are moved by `m` or deleted by 'd'.
mschieder@442:   It probably has to do how multi-selection are handled. Maybe they
mschieder@442:   are not cleared properly at the end of an operation.
mschieder@442:   One description: It happens when you have changed a lot of entries
mschieder@442:   from different projects (I assume), e.g. by editing the description,
mschieder@442:   the length or timedate and then use move where you intend to only move
mschieder@442:   one, the unwanted result is several moved entries.
mschieder@442: 
mschieder@442:   Update:
mschieder@442:   getan 2.1
mschieder@442: 
mschieder@442:   Creating a new database with test data:
mschieder@442: 
mschieder@442:   1) Delete getan_test_data.db if it already exists to create a new database.
mschieder@442:   2) Execute getan_test_data.py to get the test database getan_test_data.db.
mschieder@442:      (getan/test_data/getan_test_data.py)
mschieder@442: 
mschieder@442: - Bug 1.0
mschieder@442:   2) Open getan with the test database. (getan /path/getan_test_data.db)
mschieder@442:   3) Switch to the entries from the project pro1 with tab.
mschieder@442:   4) Mark with return and arrow keys ent1 and ent2.
mschieder@442:   5) Go back to the projects with tab.
mschieder@442:   6) Switch back to the entries of project pro1.
mschieder@442:   7) Mark this time ent3 and ent4.
mschieder@442:   8) Press m, then 3 and then y to move ent3 and ent4 to pro3.
mschieder@442: 
mschieder@442:   Expectation:
mschieder@442:     ent3 and ent4 are moved to pro3.
mschieder@442: 
mschieder@442:   Result:
mschieder@442:     ent1, ent2, ent3 and ent4 were moved to pro3.
mschieder@442: 
mschieder@442: - Bug 1.1
mschieder@442:   Execute 1) to 7) from 1.0.
mschieder@442:   8) Press d to delete ent3 and ent4.
mschieder@442: 
mschieder@442:   Expectation:
mschieder@442:       ent3 and ent4 are deleted.
mschieder@442: 
mschieder@442:   Result:
mschieder@442:     ent1, en2, ent3 and ent4 are deleted.
mschieder@442: 
mschieder@442: - Bug2
mschieder@442:   Execute 1) to 4) from 1.0.
mschieder@442:   5) Press m.
mschieder@442:   6) Now also mark ent3 and pro ent4.
mschieder@442:   7) Press 3 and then y to move ent1, ent2, ent3 and ent4 to pro3.
mschieder@442: 
mschieder@442:   Expectation:
mschieder@442:     After pressing m, you can not mark additional entries.
mschieder@442: 
mschieder@442:   Result:
mschieder@442: 	Only ent1 and ent2 are moved, though all are selected.
mschieder@442: 
bernhard@440: 20180104 BER (minor) Display licensing information with --version and
bernhard@440:   usage. Implementation idea: change this when moving away from optparse.
bernhard@440: 
bernhard@437: 20170709 BER: Give scripts/getan-eval.py a more specific name and add
bernhard@437:   it as a script to be installed.
bernhard@437: 
bernhard@428: 20170529 BER: Python compatibility: switch from deprecated optparse module
bernhard@428:   to argparse. Affects getan/main.py and scripts/getan-eval.py.
bernhard@428: 
bernhard@423: 20170504 BER: Some multi-user installations do not want a logfile by default.
bernhard@423:   We could solve this requirement by making it configurable.
bernhard@423: 
mschieder@442: 
bernhard@408: 
bernhard@440: 20160912 BER: Better code: states.py: classes EditEntryState and
bernhard@400:   AdjustEntryState have same methods exit() and set_focus(), maybe join them?
bernhard@399: 
bernhard@398: Older:
bernhard@398: 
ingo_weinzierl@23: - Create a 'Help-Widget' to give the user an information about all possible
ingo_weinzierl@23:   keys.
thomas@35: 
thomas@35: - reimplement RPN input for current getan implementation (28489e672e61)
thomas@295: 
thomas@295: - The sum of previous times and currently running time should be displayed as
thomas@295:   in previous versions of getan.
thomas@295: 
thomas@295: - The currently running time should be shown near the project.