Feature request #6965
QgsMessageLog, log levels
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
|Easy fix?:||No||Copied to github as #:||16075|
In QgsMessageLog, at the moment there are no log levels defined afaics.
logMessage takes an int argument "level", which is probably meant for this and defaults to 0.
I propose to insert an enum as follows:
#2 Updated by Médéric RIBREUX about 4 years ago
Hello, bug triage...
for the moment, there are three log levels (MessageLevel) in QgsMessaheLog: http://qgis.org/api/group__core.html#gaff7f29543072899ec0d93e1fe4d2a51d
do you consider this sufficient (and this feature request can be closed) or should we kept the feature request opened until your 5 levels are implemented ?
#5 Updated by Jürgen Fischer about 4 years ago
The idea with the log level originally was to go through all the messages and assign levels. Currently the log level is (almost?) never used - and instead of assigning levels to messages and only notify about new ones by level (not sure if info message caused a popup), the whole notification was removed - so apparently now nobody notices messages unless he explicitly looks for them or has the log window open all the time.
And so ftools for instance is accused of "silently" dropping features although it's quite noisy about it in the "invisible" message log.
#7 Updated by Médéric RIBREUX about 4 years ago
Matthias Kuhn wrote:
Btw, when you triage bugs, please set the state to "Feedback" so we can filter these later and kill the quiet ones.
I am sorry but for my account it seems that the only status that I've found are "Open" or "Closed", no "Feedback".
Should my account be "upgraded" ?