Make ErrorMsg color distinct from ServerMsg

Switch ErrorMsg to a reddish color rather than the golden hues of
ServerMsg, matching the behavior of Quasseldroid.

This helps with discovering if Auto Identify fails now that SASL
authentication errors are reported in the server buffer.  It also
points out any messages Quassel doesn't handle correctly, which might
be unexpected, but should help with discovering them.

No settings migration logic included as custom colors are an
all-or-nothing approach.  Due to 'default.qss' using a system
palette color, there's no easy way to upgrade without changing
existing colors or loading all of Qt's color palettes in startup.
For example, palette(text) is dependent upon the system theme:
ChatLine {
  foreground: palette(text);
}

diff --git a/data/stylesheets/default.qss b/data/stylesheets/default.qss
index 39ad508..8d5ae32 100644 (file)
--- a/data/stylesheets/default.qss
+++ b/data/stylesheets/default.qss
@@ -86,7 +86,7 @@ ChatLine#kick { foreground: #707070; }
 ChatLine#kill { foreground: #707070; }
 ChatLine#server { foreground: #916409; }
 ChatLine#info { foreground: #916409; }
-ChatLine#error { foreground: #916409; }
+ChatLine#error { foreground: #b30e0e; }
 ChatLine#daychange { foreground: #916409; }
 ChatLine#topic { foreground: #707070; }
 ChatLine#netsplit-join { foreground: #707070; }

diff --git a/src/qtui/settingspages/chatviewcolorsettingspage.ui b/src/qtui/settingspages/chatviewcolorsettingspage.ui
index da421bf..9c625ac 100644 (file)
--- a/src/qtui/settingspages/chatviewcolorsettingspage.ui
+++ b/src/qtui/settingspages/chatviewcolorsettingspage.ui
@@ -262,9 +262,9 @@
         </property>
         <property name="defaultValue" stdset="0">
          <color>
-          <red>145</red>
-          <green>100</green>
-          <blue>9</blue>
+          <red>179</red>
+          <green>14</green>
+          <blue>14</blue>
          </color>
         </property>
        </widget>