| Summary: | Configurations for contexts should be resolved better | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Igor Poboiko <igor.poboiko> |
| Component: | knotify | Assignee: | Olivier Goffart <ogoffart> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 4.5 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Version: 4.5 (using KDE 4.5.0) OS: Linux Some Kopete events has many contexts (for 'online' notifications these contexts are: ('account':'some account'), ('group':'Group1'), ('group':'Group2'), etc). Each context have its own configuration (by default, all are disabled, except global configuration). KNotify must resolve this situation and run an notification with some configuration (show popup, play sound, etc). The way KNotify does it now is bad. (see an example below) For example: I want to enable 'Online' notifications to all users except one of them. Logical way to do it is to enable global notifications and then go to contact notifications settings and disable it there. But when I opens contact settings, all options are unchecked there already (by default). If I'm right, the only way to do it is disabling global notifications and then enabling it for every user except the one I need. It is bad. The one way to solve it I see is to have something like priority for contexts. Configuration for some event will have some contexts, sorted by priority. The lowest priority must have global configuration. Default configuration values for some event and some context must be equals to current values for same event and context with previous (by priority) context. But with this solution there is still problem with contexts with the same priority (for example, 'group':'Group1' and 'group':'Group2') Reproducible: Always