Bruno Postle wrote: > If you add wx code to src/hugin_base then everything, even the > command-line tools, will get linked to wxwidgets.
fear not - it would be *temporary* for verbose debugging only and would never make it even into SVN - or if it will it will be commented out with a notice for developers how to activate it when they need verbosity for debug. the problem is that unlike Linux and OS X, Wincrap kills the console when a GUI app is started, so stderr output goes to the equivalent of /dev/nul. Tom directed us to a flag in MSVC when Tim started introducing verbosity to debug the issue with Celeste in the Wincrap version of Hugin. I tried toying with that flag but it messed up compiling big time. Right now I am writing to a log file, with a method introduced by Tim to debug Celeste. Unfortunately, if Hugin hangs, the buffer does not get flushed into the file and so the last bits of verbosity, which are the critical ones, are missing. Popping up alert windows gives real-time immediate feedback and enable quick identification of the source of the problem. > All this GUI stuff needs to be confined to src/hugin1. Currently it > is possible to build and install the command-line tools on a system > with no GUI libraries whatsoever (and I do this). Absolutely agreed. We should document these architectural choices somewhere. As these are my first steps into the depth of the code base, I find it an unintuitive nightmare just to locate where things are and understand why there were placed there. Yuv --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
