Hi all! I've modified hpi.py, the plugin dispatcher, to provide better information about exceptions occuring in the python plugins. This information is printed to the console (sorry, I haven't found a better way yet) and contains the type of the exception, the text of the error and a stack backtrace pointing to the precise location of the problem. Since this behaviour is in the one central location that all plugins go through, the plugins don't have to do the exception handling themselves, unless they can recover and do something else - if they fail with an exception, hpi.py will catch it and inform the user (if console output is visible).
I've slightly modified hpi.py's facility to run plugins without hugin being active. What is different now is that the result of the plugin's activity (the modified panorama) is written back into the original pto file, making it consistent with hugin's behaviour (apart from the undo facility in hugin...).This provides a convenient method to start a 'plugin-only' type plugin without starting hugin first. Try hpi.py without arguments to get a usage info. I've brushed up the plugins and done a bit of bug fixing. Amongst other things I noticed that another place in woa.py was affected by the reverse-transform-bug, so I'm working around there as well. I've added two skeleton plugins which do nothing, but show how to start out writing a 'plugin-only' plugin and a 'dual use' plugin which can also be run from the command line. Find the patch at my bazaar repo: http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch5324 Thanks to whoever picks it up! Kay -- 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
