Bug 137935 - separate History and fresh messages despite 'Group consecutive messages'
Summary: separate History and fresh messages despite 'Group consecutive messages'
Status: REPORTED
Alias: None
Product: kopete
Classification: Applications
Component: Chatwindow Styles (show other bugs)
Version: 0.40.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-26 19:52 UTC by Gavin Beatty
Modified: 2008-12-12 15:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gavin Beatty 2006-11-26 19:52:56 UTC
Version:           0.12.3 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-3 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.16-2-686

In the kopete style:
When I get a new IM from a contact, the history plugin shows my last conversation. Kopete style lumps posts from the same user into the same "paragraph", with a single timestamp. So when the contact starts a new chat, as the history is displayed, the new IM is lumped into the same "paragraph" as the old chat's last IM. This means the timestamp isn't visible.

This is quite irritating when the IM goes unnoticed for a while. One can't find out when the contact tried to chat without looking at the xml directly.
Comment 1 Dominik Tritscher 2008-07-23 13:12:46 UTC
Can't confirm that with the kopete style from kopete 0.50.80.
If some message arrives soon after the last one, it is displayed in the same paragraph as the messages bevor, but the history part is shown in some gray color per default and thus clearly different from the regular messages.
If the next message arrives somewhat later it is shown with a seperate timestamp.
Comment 2 George Kiagiadakis 2008-07-23 23:16:57 UTC
No Dominik, this "bug" still exists.  I can confirm it. I tested with a friend with msn. His last message was in 19:30 or something like that and asked him via irc to send a message again in 00:10. The message was displayed in the same "paragraph" as the last one, so I couldn't tell the time of the last message.

I guess though this bug is a wishlist item.. marking it as such.
Comment 3 Benson Tsai 2008-12-11 20:29:26 UTC
I believe if this bug: http://bugs.kde.org/show_bug.cgi?id=122600 is fixed, it will also "fix" this bug. "fix" because messages that arrive within the consecutive window will be grouped together whether or not it is part of the history, but I think that is perfectly valid behavior if not desired behavior.
Comment 4 Gavin Beatty 2008-12-12 11:10:33 UTC
It is impossible to know whether the new message is in fact new or that the old message is in fact old. Conversations almost never pick up where they left off. Also, they occasionally do not start and end with "hello" and "goodbye" respectively.

Then how are you to know without digging out the text file containing the history?

I have no kopete code available but the patch (in pseudo code) could be as simple as:

if(first message since window opened) {
  group = new Group;
}
group->addText(text);

Comment 5 Benson Tsai 2008-12-12 15:10:51 UTC
Well, I would argue that grouping them strictly by time is better than history and none history since if the conversation goes on within the window of time, maybe the user accidentally closed the chat window. Also there is already a way to tell history from none history: you have the option the option to gray out history text.