Just to make sure you are aware of this functionality: the current  code logs lots and lots of tracing activity in openwsn-sw\software\openvisualizer\bin\moteStateGui\moteStateGui.log.

All the components use log.debug(), log.warning(), log.error() and log.critical() to signal something. The configuration file openwsn-sw\software\openvisualizer\bin\moteStateGui\logging.conf configures which of these logging sources are active, i.e. which components and for each component at what debugging level.

I believe that this method is better for tracing the execution of a program (and debugging what happened just before a crash) that printing to the terminal since the log statements stay in the source code forever, and just the configuration file needs be updated to enable/disable some logs. With prints, we would need to constantly comment out and add remove as we are working on parts.

Could you please let me know wether this logging capability satisfies your requirements, and if not, why print statements make more sense?

Thanks!