Bug 256635 - Konversation doesn't highlight taskbar entry
Summary: Konversation doesn't highlight taskbar entry
Status: RESOLVED WORKSFORME
Alias: None
Product: kde-windows
Classification: Miscellaneous
Component: other (show other bugs)
Version: 4.10
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-11 22:50 UTC by Arkadiusz Piekarz
Modified: 2021-03-10 06:36 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 Arkadiusz Piekarz 2010-11-11 22:50:54 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                MS Windows

Konversation doesn't highlight its taskbar entry when configured in notifications panel to do that, for instance when someone writes user's nick in a message. 

Reproducible: Always

Steps to Reproduce:
1. Go to Settings -> Configure Notifications
2. Select some events, for instance "Highlight triggered" or "Nick written", then check the checkbox "Mark taskbar entry".
3. Make the event happen in some way, i.e. ask someone to write your nick in the chat.
4. Before that happens, switch to other application, so that Konversation is not the active one and wait for the event.

Actual Results:  
When the event (that should trigger marking the taskbar) happens, the taskbar entry is not highlighted.

Expected Results:  
Taskbar entry should have been highlighted when the event occured.

Tested with KDE 4.4.4 with Konversation 1.3 on Windows 7.
Comment 1 Dirk Wallenstein 2012-01-02 10:14:43 UTC
Note that there is a configuration option in Behavior->General (at the top).  It's a bit hidden IMHO.  And I don't know if the description really matches.
Comment 2 Patrick Spendrin 2013-06-01 21:31:40 UTC
Still broken in KDE 4.10.2
Comment 3 Justin Zobel 2021-03-09 23:01:51 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.