https://bugs.kde.org/show_bug.cgi?id=521945
--- Comment #1 from Jonathan Marten <[email protected]> --- I would suggest that, in the interest of reducing duplication and confusion, some of these events could be combined. "Fatal Error", "Catastrophe" and "Critical Message" could be combined into a "Fatal Error - There was a serious error causing a program to exit". "Fatal and "Critical" imply a similar level of problem, at least in English, but "Catastrophe" is not a word which is often used in this technical context. Similarly "Warning" and "Warning Message" could be combined into "Warning - A program detected a problem but is able to continue". A new category should be added "Error - The program detected an error but is able to continue running" with sound "dialog-error". The difference between a "warning" and "error" should be that a "Warning" means that some or part of the user's requested actions could be carried out, but a "Error" means that nothing could be done. For example, when copying mutiple files in a file manager, "Warning - Not all of the files could be copied" "Error - The files could not be copied (because...)" Obviously, to maintain API compatibility existing well known event ID strings or KNotification::StandardEvent values should be mapped onto appropriate new values: StandardEvent::Warning -> messageWarning StandardEvent::Error -> messageError StandardEvent::Catastrophe -> messageCritical "warning" -> messageWarning "catastrophe" -> messageCritical "fatalerror" -> messageCritical "error" -> messageError -- You are receiving this mail because: You are watching all bug changes.
