Add comment on why we surpress some of those log messages

This commit is contained in:
Nicolas Werner 2020-04-08 23:12:18 +02:00
parent 6794b6472d
commit 4fa12b52aa

View file

@ -25,12 +25,18 @@ qmlMessageHandler(QtMsgType type, const QMessageLogContext &context, const QStri
const char *file = context.file ? context.file : ""; const char *file = context.file ? context.file : "";
const char *function = context.function ? context.function : ""; const char *function = context.function ? context.function : "";
// Surpress binding wrning for now, as we can't set restore mode to keep compat with qt 5.10 if (
if (msg.endsWith( // Surpress binding wrning for now, as we can't set restore mode to keep compat with
"QML Binding: Not restoring previous value because restoreMode has not been set.This " // qt 5.10
"behavior is deprecated.In Qt < 6.0 the default is Binding.RestoreBinding.In Qt >= " msg.endsWith(
"6.0 the default is Binding.RestoreBindingOrValue.") || "QML Binding: Not restoring previous value because restoreMode has not been set.This "
msg.endsWith("Both point size and pixel size set. Using pixel size.")) "behavior is deprecated.In Qt < 6.0 the default is Binding.RestoreBinding.In Qt >= "
"6.0 the default is Binding.RestoreBindingOrValue.") ||
// The default style has the point size set. If you use pixel size anywhere, you get
// that warning, which is useless, since sometimes you need the pixel size to match the
// text to the size of the outer element for example. This is done in the avatar and
// without that you get one warning for every Avatar displayed, which is stupid!
msg.endsWith("Both point size and pixel size set. Using pixel size."))
return; return;
switch (type) { switch (type) {