| Summary: | Alphabetic order of tasks | ||
|---|---|---|---|
| Product: | [Applications] ktimetracker | Reporter: | Dirk Hoffmann <hoffmann> |
| Component: | general | Assignee: | Zoltan Gyarmati <mr.zoltan.gyarmati> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | mr.zoltan.gyarmati |
| Priority: | NOR | ||
| Version: | Git (master) | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Dirk Hoffmann
2010-02-01 13:37:33 UTC
I agree. I did not change that and will confirm this bug as soon as I have reproduced it. confirmed Unfortunately this bug is still present in 4.4. A related feature is the opening of subtasks with the [+]/[-] button in the table. I assume that this should be treated simultaneously with the present bug: When a collapsed item lies at the bottom of the visible window and is expanded by clicking on the [+] button, then it may happen that not all subtasks become visible, because the subtask list is too long. When expanding a task, the last subtask should always be constrained to appear at least the bottom of the window (or higher)! (This was also well handled in karm already, so why did it disappear?) Maybe this helps to write a patch: http://doc.qt.nokia.com/latest/qstringmatcher.html#setCaseSensitivity Maybe qsortfilterproxymodel has an option for that. See also bug 285160 Patch to fix this sent for review as: https://git.reviewboard.kde.org/r/121369/ ID: 10c7cfb2aaf239c57d5e244ef7455a26732d0ba9 ktimetracker: sort progress percentage numerically and tasks case-insensitively REVIEW: 121369 |