On 2013.06.27 14:49, Toby Gray wrote: > This change makes it considerably easier to debug issues in UI applications > which don't necessarily have a console connected to stderr.
I like that idea. That's something I've been using for Rufus, and it can come quite handy for pure GUI apps indeed. > Outputting to the debugger shouldn't occur in normal situations so > this change has to be explicitly enabled by a build-time config flag. I guess that makes sense, since UI apps wouldn't have commandline parameters to toggle the option, and using a global variable wouldn't be of much use either. However, I don't think hijacking ENABLE_DEBUG_LOGGING is the way to go. Some people may still want to use ENABLE_DEBUG_LOGGING to force debug logging to the console on Windows, and we would break the behaviour of any app that was configured with that. I'd go for USE_OS_LOGGING_FACILITY or something, and a configure option in the same vein to make it as explicit as possible what the intent is here, especially as some people may only want error and warnings, and not debug, to be directed to the OS logging facility. And of course, this may also make it more suitable for other OSes to implement a similar option (eg. direct output to one of the log facilities on Linux). Regards, /Pete ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
