Bug 191019 - reading messages in non-active chat difficult
Summary: reading messages in non-active chat difficult
Status: RESOLVED INTENTIONAL
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 0.70.2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-29 11:50 UTC by arne anka
Modified: 2016-07-13 11:19 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description arne anka 2009-04-29 11:50:03 UTC
Version:           0.70.2 (using 4.2.2 (KDE 4.2.2), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28

assume, there's no chatwindow yet.
a message comes in, the notification pops up (without buttons, see 191012).
immediately, two issues are raised:
a) how to read that message? either via minimize/maximize, see 191012 or via clicking the rotating systray icon.
clicking the systray icon produces the kopete main window (contacts list and all), only double clicking finally produces a chat window -- and still the main window.

b) if you aren't fast enough, the notification disappears -- what do you do now? usually the systray icon still should rotate, but i got the impression, sometimes it just stops. and apparently how long the notification stays visible is a matter of random, just noticed one message disappearing after maybe 3secs, and the next one staying there for apparently ever.

suggestions:
for a)
besides fixing 191012 which is clearly a bug, in case of unread messages a single click should immediately produce a chatwindow with the chat the message belongs to. 
in case of multiple messages for different chats, several chat windows or tabs, with the most recent one on top/with focus.

b) notification should not disappear resp the delay should be configurable -- i am not quite sure, if i understood the report right, but that already might be addressed.
Comment 1 arne anka 2016-07-13 11:19:16 UTC
stopped using ist a long time ago