Bug 47127 - korganizer doesn't save todo list column header prefs.
Summary: korganizer doesn't save todo list column header prefs.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdepim
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-03 12:42 UTC by Mike A. Harris
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-07-13 12:52:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike A. Harris 2001-07-03 12:42:28 UTC
Description of Problem:
In Korganizer the todo list on the left side has default column headers
"Summary   Priority    Due Date".  I drag and drop priority to the first
column and it works.  If I exit korganizer and restart it has forgotten
my column reordering.  This makes the whole point of customizing the
order useless.  Using save settings in the pulldown menu also doesn't help.

How Reproducible: 100%


Steps to Reproduce:
1. View TODO/Week view
2. Drag the priority column over to the left in front of "Summary"
   and let go.  It now moves there in front.
3. Hit save settings in the pulldown menu at top.
4. Quit Korganizer and restart.


Actual Results:
Columns have reset to factory defaults.  ;o)

Expected Results:
My settings are remembered.  I shouldn't have to manually tell it to
save them either it should just remember that I moved the columns like
user friendly Windows applications would.  ;o)

Additional Information:
Windows 95 CD's make good coasters for protecting your desk against
hot drinks.

Comment 1 Mike A. Harris 2002-06-22 04:57:48 UTC
Korganizer basically sucks, and seems unmaintained upstream.  No real point
in keeping this bug open as it probably isn't a high priority item to fix,
and not likely to get fixed upstream.  Evolution and other software seem
much better for this sort of thing.

In lieu of a CLOSED->REPORTER_DOESNT_CARE_ANYMORE resolution, I've chosen
CLOSED->WONTFIX.  ;o)


Note You need to log in before you can comment on or make changes to this bug.