Bug 191556 - Default sorting isinvalid
Summary: Default sorting isinvalid
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 05:34 UTC by Alexander Darovsky
Modified: 2017-01-07 21:38 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Darovsky 2009-05-04 05:34:01 UTC
Version:           1.4.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-11-generic

When I run akregator at first time, I see weird look:

1. "Feeds" column in feeds tree is small, and does not stretch when pane is resized. This is the largest column, and is expected to resize appropriately.

2. "Title" column in articles list has the same problem. "Date" column is auto resized, while it is not needed: time has fixed length, while title often does not fit into column.

3. Default sorting is on "title", while normally it is on "Date" in reverse order.
Comment 1 Alexander Darovsky 2009-05-04 05:35:35 UTC
Please read "while normally it is on "Date" in reverse order" as "while normally it should be on "Date"
Comment 2 FiNeX 2009-05-06 23:21:36 UTC
The first issue has been fixed on current trunk. I don't know if it will be backported on 4.2.3. Anyway 4.3 will be fine. I've updated the summary of the bug.
Comment 3 Denis Kurz 2016-09-24 19:40:47 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 akregator (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:38:31 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.