Bug 261193 - Activity order is reversed on restart
Summary: Activity order is reversed on restart
Status: RESOLVED DUPLICATE of bug 251614
Alias: None
Product: plasma4
Classification: Unmaintained
Component: activities (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-25 01:39 UTC by Kai Uwe Broulik
Modified: 2011-12-03 13:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
activities ordering idea (42.27 KB, image/png)
2011-01-28 13:53 UTC, FiNeX 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2010-12-25 01:39:45 UTC 
Version:           unspecified (using KDE 4.5.90) 
OS:                Linux

I just added three activities in this order “home”, “work”, “studying”. I restarted my computer and then the order was “studying”, “work”, “home”.
Remember the order correctly.

Reproducible: Didn't try
Comment 1 mursusoft 2011-01-04 15:22:22 UTC 
Yeah I got this too and sometimes they go back to normal order. I guess ability to sort them would be nice...
Comment 2 Chani 2011-01-04 16:12:23 UTC 
patches welcome. :) we just haven't got around to putting in any sorting code.

I'm also unsure whether sorting ought to be done centrally, or by every bit of UI that shows them... and it would be a bit silly to have a config UI just for choosing how to sort them, it ought to be available through d&d... can anyone think of an elegant solution?
Comment 3 Kai Uwe Broulik 2011-01-04 22:01:18 UTC 
What about just being able dragging them around? ;)
Comment 4 Chani 2011-01-04 23:12:44 UTC 
yeah maybe that is enough... :)
Comment 5 FiNeX 2011-01-28 13:53:55 UTC 
Created attachment 56571 [details]
activities ordering idea

Something like this??

P.S the activity bar should use the same order
Comment 6 Gregor Tätzner 2011-12-03 13:35:44 UTC 
Seemingly this issue mutated to a feature request.

*** This bug has been marked as a duplicate of bug 251614 ***