Summary: | wish: remove or simplify the ability to load different files | ||
---|---|---|---|
Product: | [Applications] ktimetracker | Reporter: | Diederik van der Boor <vdboor> |
Component: | general | Assignee: | Thorsten Staerk <dev> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | andreas.karrenbauer, hoffmann, langec, mityok |
Priority: | NOR | ||
Version: | Git (master) | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.8 |
Description
Diederik van der Boor
2009-01-29 16:34:08 UTC
Good points, I have never seen it like this. When ktimetracker was still karm, it was exactly that way and we changed it. I think it is great that you can open/save/backup your ics file. And if you do not care, you just start ktimetracker and can add tasks and timetrack them. So atm I do not make a decision. I do not completely understand Diederik's points regarding file saving. However, there would be one feature going with any improvement of the save/load interface: Allow user selection of the tasks which are imported from another iCal file, not only import the complete file. The same holds true for export as well. :-} ... and best would even be with drag&drop between 2 ktimetracker instances. removed connection to closeFile() and newFile() in timetrackerwidget.cpp. Cleanup needed. removed close and new from ktimetrackerui.rc removed close and new from d->mActions in timetrackerwidget.cpp Git commit d032c2c279f0c15bac1f0a3143d0df4bb2437f4b by Thorsten Staerk. Committed on 21/09/2011 at 07:35. Pushed by tstaerk into branch 'master'. remove "New" and "Close" functionality BUGS:182317,265085 M +0 -4 ktimetracker/ktimetrackerui.rc M +0 -7 ktimetracker/timetrackerwidget.cpp http://commits.kde.org/kdepim/d032c2c279f0c15bac1f0a3143d0df4bb2437f4b *** Bug 190367 has been marked as a duplicate of this bug. *** *** Bug 193220 has been marked as a duplicate of this bug. *** *** Bug 269767 has been marked as a duplicate of this bug. *** *** Bug 235039 has been marked as a duplicate of this bug. *** |