Ticket #74 (closed task: fixed)

Opened 11 years ago

Last modified 10 years ago

xuvtools: re-implement the logging-facility

Reported by: ne704 [niko@… Owned by: emmenlau
Priority: major Milestone:
Component: xuvtools Version:
Keywords: xuvtools Cc: aaron@…, niko@…, mario@…


Logging should be re-implemented as discussed on the phone to address the stdout/stderr issue and the problems of (re-)opening/closing/redirecting those file descriptors as well as to ease the verbosity-filtering, e.g. by using a singleton logging-object.

Change History

Changed 11 years ago by ne704 [niko@…

I'd very much appreciate if the "Output console" messages were also handled by the logger, as well as the statusbar-stuff (having three different variants of calling statusreport-functions is a real PITA).

Cheers, Niko

Changed 11 years ago by emmenlau

Can you explain what messages you are missing, and where (examples)? I would have guessed the order is:

  • all messages go to logfile
  • all messages with verbosity <= "advanced settings verbosity" go to the output console
  • all messages with very urgent verbosity go to status bar

That would define an order where the logfile is always complete, and the user is less spammed.

Changed 10 years ago by emmenlau

  • cc aaron@… added
  • status changed from new to closed
  • resolution set to fixed

Closing this bug since the basic functionality is available since revision r3030 (changes include multiple prior revisions).

Note: it would be good to add libReporter to all LMB libraries. Currently it is only present in xuvtools and xuvtools_gui. However, adding libReporter to all libraries would create a new dependency, so a define HAVE_REPORTER or similar should be used.

Note: See TracTickets for help on using tickets.