Bug 127962

Summary:	wrong order of menu items in settings menu?
Product:	[Applications] akregator	Reporter:	Frederik Schwarzer <schwarzer>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	christophe
Priority:	NOR
Version:	1.2.2
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description Frederik Schwarzer 2006-05-24 20:03:05 UTC

Version:           1.2.2 (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The order of the menu items in settings menu differs from all other KDE applications I have seen so far.
In those the "Configure [Application]" item is the last one. In akregator there are still two other items below that. I think it would be better to have that consistent in all KDE applications.

Comment 1 Frank Osterfeld 2006-05-24 20:15:29 UTC

That was fixed by Ismail Onur Filiz. (i.e. it will be fixed in the upcoming 3.5.3).

Comment 2 Frederik Schwarzer 2006-05-24 21:42:13 UTC

Thanks for informing.
As I just saw, the order is not only wrong for this item.
When I look at the Settings menu of Konversation, KMail and akregator, I see it as follows:
Konversation
  Shortcuts
  Toolbars
  Notifications
  Konversation

KMail
  Shortcuts
  Notifications
  Toolbars
  KMail

Akregator
  Notifications
  Akregator
  Shortcuts
  Toolbars

Not knowing about any guidelines for menu order in KDE I cannot say what programm is against those rules, but I find it kind of confusing.

Comment 3 Frederik Schwarzer 2006-09-13 21:41:37 UTC

I do not know if reopening is appreciated here, but I do so anyway and hide behind  my monitor then. ;)

In version 1.2.4 (KDE 3.5.4) the order of those entries is still in old state here.

Comment 4 Frank Osterfeld 2006-09-14 07:46:55 UTC

Confirmed, the order is even wrong with a fresh install here, so it's not a problem with custom rc files of a user not updated correctly.

Comment 5 Christophe Marin 2009-03-07 12:46:08 UTC


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