Hi all, To give my (personal) viewpoint on these critical bugs on the OSX "side":
2297456 Hugin crashes on exit after use OpenGL fast preview window<http://sourceforge.net/tracker/?func=detail&aid=2297456&group_id=77506&atid=550441>: Still happens all the time after it has been used. 2189798 syslogd on OS X gets crazy<http://sourceforge.net/tracker/?func=detail&aid=2189798&group_id=77506&atid=550441>: Can be closed. Ippei built in some extensive (debug) logging (and so did some other programmers). I "out commented" most of it (svn *3593*<http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3593>) and the syslog is no longer flooded. 2152269 Crash on MacOS when deleting control points<http://sourceforge.net/tracker/?func=detail&aid=2152269&group_id=77506&atid=550441>. Can be closed? I can't reproduce this one, not even with a couple of very big projects, trying a couple of builds. 1969739 [OSX] jpeg quality setting by user is not read correctly<http://sourceforge.net/tracker/?func=detail&aid=1969739&group_id=77506&atid=550441>. Still not solved. It's mentioned as a duplicate but I can't find the other. The work-around is to set the jpeg-quality. Click another text-field, click the jpeg-quality textfield again and then it's used. 1898264 autopano-sift-c failure with Hugin.app (OS X)<http://sourceforge.net/tracker/?func=detail&aid=1898264&group_id=77506&atid=550441>. Should be closed. This must be a configuration "error". Stupid OSX holds a special path in a special file for external binaries called from a bundle application. A "quality passed" OSX bundle should only use OSX standard libraries and binaries outside the bundle. However, when a binary inside a bundle is started from the command line using the full path to it (as specified in the ticket), the normal PATH is used (Who at Apple was so stupid to design it like that). It works fine in all combinations I tried (using that "special" bundle path that's not in the normal environment). Harry 2009/6/9 Bruno Postle <[email protected]> > > On Tue 09-Jun-2009 at 02:58 -0700, Yuv wrote: > > > >I see there are two grouping facilities on the (new?) SF bugtracker: > >Category and Group. I am a bit confused about the criteria. Maybe we > >need a clean up there? But first the most pressing question: am I > >right to assume that the group "hugin-critical" is what needs to be > >solved before we can release 0.8.0? > > The categories and groups just narrow things down. > > I use categories are to indicate if the bug is platform specific > (Linux, OS X, Windows), and groups for the various tools, i.e. a > large number of entries in the hugin tracker are actually enblend or > autopano-sift-c bugs. > > > > https://sourceforge.net/tracker/?limit=100&group_id=77506&atid=550441&status=1&artgroup=801640 > > > >there are 25 tickets open there. Let's work them down! > > I don't think any of these are actually release blockers or are not > going to be fixed anytime soon. > > ..however there are a couple of uncategorised recent items that > should be in this 'critical' group. > > -- > Bruno > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
