Bug 209471

Summary:	Akregator - Column Sorting Arrows Indicate Behaviour Reverse of that Expected
Product:	[Applications] kontact	Reporter:	dlesage <dlesage>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	4.3
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Column Sort Arrows Showing Opposite Behaviour to that Expected - 1. Column Sort Arrows Showing Opposite Behaviour to that Expected - 2.

Description dlesage 2009-10-05 01:29:30 UTC

Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Fedora RPMs

Description of problem:
If one sorts feeds by date (by clicking on the column header), when the arrow
is pointing DOWN, the most recent entry is at the TOP.  When the arrow is
pointing UP, the most recent entry is at the BOTTOM.  Shouldn't this be the
other way around?  It is contrary to most other programs and certainly GTK ones
are the opposite.

The theme installed was KDE-Leonidas.


Version-Release number of selected component (if applicable):
Akregator 1.5.0 (KDE 4.3.0).

How reproducible:
Every time.

Steps to Reproduce:
1. yum install kdepim. (Pulls down KDE Leonidas theme as a dependency.)
2. Import *.opml.
3. Fetch all feeds.  
4. Click on date column heading to sort articles.

Actual results:
DOWN = Most recent article at top.
UP = Most recent article at bottom.

This is the opposite of the convention across most other software.

Expected results:
DOWN = Most recent article at bottom.
UP = Most recent article at top.

Comment 1 dlesage 2009-10-05 01:31:06 UTC

Created attachment 37368 [details]
Column Sort Arrows Showing Opposite Behaviour to that Expected - 1.

Comment 2 dlesage 2009-10-05 01:31:45 UTC

Created attachment 37369 [details]
Column Sort Arrows Showing Opposite Behaviour to that Expected - 2.

Comment 3 Denis Kurz 2016-09-24 19:24:11 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:42:55 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.