Mercurial > getan
comparison doc/old_issues.txt @ 450:45b7b83efaed
Prepares for release 2.2.
| author | Magnus Schieder <mschieder@intevation.de> |
|---|---|
| date | Fri, 26 Jan 2018 13:15:34 +0100 |
| parents | |
| children | 050ffdec60d9 |
comparison
equal
deleted
inserted
replaced
| 449:50b00768575e | 450:45b7b83efaed |
|---|---|
| 1 20180117 Magnus Schieder | |
| 2 | |
| 3 20170317 BER: Reproduce and then fix a defect that it is surprising which | |
| 4 entries are moved by `m` or deleted by 'd'. | |
| 5 It probably has to do how multi-selection are handled. Maybe they | |
| 6 are not cleared properly at the end of an operation. | |
| 7 One description: It happens when you have changed a lot of entries | |
| 8 from different projects (I assume), e.g. by editing the description, | |
| 9 the length or timedate and then use move where you intend to only move | |
| 10 one, the unwanted result is several moved entries. | |
| 11 | |
| 12 reproduced with getan 2.1 | |
| 13 20180118BER Reproduced with urwid v1.3.0, python3.4.6, getan 2.2.dev1 r445 | |
| 14 | |
| 15 Creating a new database with test data: | |
| 16 | |
| 17 1) Delete getan_test_data.db if it already exists to create a new database. | |
| 18 2) Execute getan_test_data.py to get the test database getan_test_data.db. | |
| 19 (getan/test_data/getan_test_data.py) | |
| 20 | |
| 21 - Bug 1.0 | |
| 22 2) Open getan with the test database. (getan /path/getan_test_data.db) | |
| 23 3) Switch to the entries from the project pro1 with tab. | |
| 24 4) Mark with return and arrow keys ent1 and ent2. | |
| 25 5) Go back to the projects with tab. | |
| 26 | |
| 27 20180118BER: | |
| 28 Observation: ent1 and ent2 are not highlighted anymore. | |
| 29 | |
| 30 6) Switch back to the entries of project pro1. | |
| 31 7) Mark this time ent3 and ent4. | |
| 32 8) Press m, then 3 and then y to move ent3 and ent4 to pro3. | |
| 33 | |
| 34 Expectation: | |
| 35 ent3 and ent4 are moved to pro3. | |
| 36 | |
| 37 Result: | |
| 38 ent1, ent2, ent3 and ent4 were moved to pro3. | |
| 39 | |
| 40 - Bug 1.1 | |
| 41 Execute 1) to 7) from 1.0. | |
| 42 8) Press d to delete ent3 and ent4. | |
| 43 | |
| 44 Expectation: | |
| 45 ent3 and ent4 are deleted. | |
| 46 | |
| 47 Result: | |
| 48 ent1, en2, ent3 and ent4 are deleted. | |
| 49 | |
| 50 |