The documentation (https://doc.qt.io/qt-6/qtlogging.html) states:
*The default pattern is %{if-category}%{category}: %{endif}%{message}*
1) In my limited experience most or all logging architectures print the
type (aka. severity or criticality, e.g. warning, debug, info, etc.) by
default.
2)
critical}C%{endif}%{if-fatal}F%{endif}|%{message}
>
> See https://doc.qt.io/qt-6/qtlogging.html#qSetMessagePattern for details.
> Whatever format you apply in this way will be followed by Qt and (unless it
> overrides, which is unlikely) QGIS as well.
>
> Alexey
>
> On Sun, 2023
day, 10 December 2023 09:47:22 PST Thomas Larsen Wessel wrote:
> > I'm actually grateful that the original message is so concise, otherwise
> I
> >
> > > wouldn't look for a way to customise it
> >
> > I never considered that. If the goal is to make ap
Quote from https://doc.qt.io/qt-6/qt-embedded-fonts.html:
*Qt normally uses fontconfig to provide access to system fonts*. If
> fontconfig is not available, e.g. in dedicated embedded systems where space
> is at a premium, Qt will fall back to using QBasicFontDatabase. In this
> case, Qt applicati
at 7:53 PM Allan Sandfeld Jensen
wrote:
> On Samstag, 16. Dezember 2023 15:58:00 CET Thomas Larsen Wessel wrote:
> > Quote from https://doc.qt.io/qt-6/qt-embedded-fonts.html:
> >
> > *Qt normally uses fontconfig to provide access to system fonts*. If
> >
> > > fontc
