Mercurial > getan
changeset 444:08b61b78285d
TODO: add multi-selection Bug report.
author | Magnus Schieder <mschieder@intevation.de> |
---|---|
date | Thu, 18 Jan 2018 13:07:35 +0100 (2018-01-18) |
parents | dc79952b36b0 |
children | a47c7c0e01ec |
files | TODO |
diffstat | 1 files changed, 58 insertions(+), 9 deletions(-) [+] |
line wrap: on
line diff
--- a/TODO Thu Jan 18 11:29:29 2018 +0100 +++ b/TODO Thu Jan 18 13:07:35 2018 +0100 @@ -1,3 +1,61 @@ +20180117 Magnus Schieder + + 20170317 BER: Reproduce and then fix a defect that it is surprising which + entries are moved by `m` or deleted by 'd'. + It probably has to do how multi-selection are handled. Maybe they + are not cleared properly at the end of an operation. + One description: It happens when you have changed a lot of entries + from different projects (I assume), e.g. by editing the description, + the length or timedate and then use move where you intend to only move + one, the unwanted result is several moved entries. + + Update: + getan 2.1 + + Creating a new database with test data: + + 1) Delete getan_test_data.db if it already exists to create a new database. + 2) Execute getan_test_data.py to get the test database getan_test_data.db. + (getan/test_data/getan_test_data.py) + +- Bug 1.0 + 2) Open getan with the test database. (getan /path/getan_test_data.db) + 3) Switch to the entries from the project pro1 with tab. + 4) Mark with return and arrow keys ent1 and ent2. + 5) Go back to the projects with tab. + 6) Switch back to the entries of project pro1. + 7) Mark this time ent3 and ent4. + 8) Press m, then 3 and then y to move ent3 and ent4 to pro3. + + Expectation: + ent3 and ent4 are moved to pro3. + + Result: + ent1, ent2, ent3 and ent4 were moved to pro3. + +- Bug 1.1 + Execute 1) to 7) from 1.0. + 8) Press d to delete ent3 and ent4. + + Expectation: + ent3 and ent4 are deleted. + + Result: + ent1, en2, ent3 and ent4 are deleted. + +- Bug2 + Execute 1) to 4) from 1.0. + 5) Press m. + 6) Now also mark ent3 and pro ent4. + 7) Press 3 and then y to move ent1, ent2, ent3 and ent4 to pro3. + + Expectation: + After pressing m, you can not mark additional entries. + + Result: + Only ent1 and ent2 are moved, though all are selected. + + 20180104 BER (minor) Display licensing information with --version and usage. Implementation idea: change this when moving away from optparse. @@ -10,15 +68,6 @@ 20170504 BER: Some multi-user installations do not want a logfile by default. We could solve this requirement by making it configurable. -20170317 BER: Reproduce and then fix a defect: that it is surprising which - entries are moved by `m` or deleted by 'd'. - It probably has to do how multi-selections are handled. Maybe they - are not cleared properly at the end of an operation. - One description: It happens when you have changed a lot of entries - from different projects (I assume), e.g. by editing the description, - the length or timedate and then use move where you intend to only move - one, the unwanted result is several moved entries. - 20160912 BER: Better code: states.py: classes EditEntryState and AdjustEntryState have same methods exit() and set_focus(), maybe join them?