--Boundary-00=_rc23IKwv/fyQVuV Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi kopete devs, I've got problems with history plugin - when history is shown, messages get= =20 reordered based on their arrival time. However, at least some protocols (IC= Q)=20 use remote user's clock for recording arrival time, which results in messed= up=20 history when your buddy's clock is skewed. This small patch just removes the reordering mechanism, as messages are=20 already in correct order in history files (e.g. semantically chronological,= =20 even when recorded arrival times are messed up) The patch is based on kopete 4.1.1, should apply to trunk too. Mat=C4=9Bj Laitl --Boundary-00=_rc23IKwv/fyQVuV Content-Type: text/x-patch; charset="utf-8"; name="kopete-nosort-history.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="kopete-nosort-history.patch" diff --git a/kopete/plugins/history/historylogger.cpp b/kopete/plugins/history/historylogger.cpp index 5a3a9bd..e366c4c 100644 --- a/kopete/plugins/history/historylogger.cpp +++ b/kopete/plugins/history/historylogger.cpp @@ -391,17 +391,8 @@ QList HistoryLogger::readMessages(QDate date) .arg( dt.toString(Qt::LocalDate), msg.escapedBody() )); msg.setTimestamp( dt ); msg.setDirection( dir ); - - // We insert it at the good place, given its date - QList::Iterator msgIt; - - for (msgIt = messages.begin(); msgIt != messages.end(); ++msgIt) - { - if ((*msgIt).timestamp() > msg.timestamp()) - break; - } - messages.insert(msgIt, msg); + messages.append(msg); } } --Boundary-00=_rc23IKwv/fyQVuV Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel --Boundary-00=_rc23IKwv/fyQVuV--