Saving, Loading and Groups and write the rules of the first two tabs to ~/.config/QtProject/qtlogging.ini. Only the categories that differ from their default severity are written, which keeps the file short and lets applications change their own defaults later.
opens a read only window showing the qtlogging.ini that and would write, without writing anything. Since it applies the same rule as they do, it is also the quickest way to see which categories were left out because they still sit at their default severity.
The remaining buttons manage rule sets you want to keep side by side, for instance one per bug you are chasing:
exports the current rules to a
.kdebugsettingsrulesfile anywhere on disk. asks for a name and stores the rules as a group in~/.local/share/kdebugsettings/groups/.Unlike , both write out every category, not only the modified ones, so that reloading the file restores exactly the state you saved.
reads back a
.kdebugsettingsrulesfile, offers the saved groups in a submenu, and opens a dialog where groups can be renamed, removed and exported. Loading only fills the dialog; use or to actually activate the rules.Reads an additional
.categoriesfile and adds the categories it declares to the KDE Application tab. This is useful for an application that is not installed system wide, typically one you are building yourself.