Bug 187561 - Natural message order in History
Summary: Natural message order in History
Status: REPORTED
Alias: None
Product: kopete
Classification: Applications
Component: History Plugin (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-19 01:36 UTC by Alexey Chernov
Modified: 2009-03-19 10:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Chernov 2009-03-19 01:36:32 UTC 
Version:            (using KDE 4.2.1)
Compiler:          GCC 4.3.2 Target: x86_64-unknown-linux-gnu Configured with:  ../gcc-4.3.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,fortran,objc,treelang --disable-multilib --enable-c99 --enable-long-long Thread model: posix
OS:                Linux
Installed from:    Compiled From Sources

I think it should be better not to sort messages in History by time, because if users have not synchronized clock (very often case) the history become almost unusable, answers go before questions :) It's better to write them in the order they appeared in the chat window, for example, to sort all the messages by the local side's time (now remote answers are obviously have remote side's time).