So what I was getting at is that could it be that most of the problems of the layout branch like: windows-image-read-crash, EXIF-bug, cropfactor-FOV-bug, are actually code-baseline issues for that track that would be mostly overcome after a merge into a more mature code-track.
While the really new features that needs fixing and testing are maybe aligned-stack-optimization-crash and even more so testing that the new parameter model holds for all different panoramic purposes I have reported problems of the layout view itself, but this bug only limits usefulness, and is not blocking a release IMHO. (although important for my application) I was getting at what is absolutely necessary to do with layout branch to quickly get it merged. Once that has been done, it is easier to build improvements on that. > > --~--~---------~--~----~------------~-------~--~----~ 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
