Hi, This is just a heads up that https://codereview.qt-project.org/#change,44430 is now ready to be reviewed from my side ;) So feel free to have a look.
If you don't know what the patch is actually about, I recommend to check out the included example: https://codereview.qt-project.org/#patch,sidebyside,44430,16,examples/logging/logger/main.cpp https://codereview.qt-project.org/#patch,sidebyside,44430,16,examples/logging/logger/logrules.txt Regards Kai > -----Original Message----- > From: development-bounces+kai.koehne=digia....@qt-project.org > [mailto:development-bounces+kai.koehne=digia....@qt-project.org] On > Behalf Of Koehne Kai > Sent: Monday, August 26, 2013 4:38 PM > To: Blasche Alexander; Robin Burchell; development@qt-project.org > Cc: Poenitz Andre > Subject: Re: [Development] Tracing Qt > [...] > I actually started a patch back in January that I just revived: > > https://codereview.qt-project.org/#change,44430 > > There are certainly still rough edges, but IMO we should be able to re-use > some of it for a hypothetical tracing solution, too. The actual data flow > will be > different from the logging case (you don't want to go through > QMessageLogger etc, and don't want to convert everything to a QString in > the first place), but the idea that you can activate/deactivate categories at > runtime through different means is the same. > > Regards > > Kai > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development