Mercurial > getan
view TODO @ 439:3103429ec963
Makes 'move' operation more consistent.
* Improves 'move' operation to work in the current entry, if there is no
selection. This is more consistent with 'delete'. Patch by Frank Koormann.
* Removes two superfluous methods in controller.
* Improves README: Adds Frank Koormann as contributor. Better phrasing
for the license indication.
* TODO: Details problem with multi-selections.
author | Bernhard Reiter <bernhard@intevation.de> |
---|---|
date | Wed, 13 Sep 2017 09:06:28 +0200 |
parents | 70063d348739 |
children | f441913a5cdc |
line wrap: on
line source
20170709 BER: Give scripts/getan-eval.py a more specific name and add it as a script to be installed. 20170529 BER: Python compatibility: switch from deprecated optparse module to argparse. Affects getan/main.py and scripts/getan-eval.py. 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-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. 20160912 BER: Better code: states.py: classes EditEntryState and AdjustEntryState have same methods exit() and set_focus(), maybe join them? Older: - Create a 'Help-Widget' to give the user an information about all possible keys. - reimplement RPN input for current getan implementation (28489e672e61) - The sum of previous times and currently running time should be displayed as in previous versions of getan. - The currently running time should be shown near the project.