On Wednesday, April 22, 2015 at 5:56:13 AM UTC-4, Bruno Postle wrote: > > > > On 22 April 2015 08:15:15 BST, David W. Jones wrote: > >On 04/21/2015 04:11 PM, Terry Duell wrote: > > >I'd think it eminently suited for situations where you use one machine > >with GUI to create and config PTO files (perhaps a LOT of them), then > >hand them off to other machines to stitch without requiring the other > >machines to run a GUI. Or maybe the idea is that stitching must now > >REQUIRE interactive use, rather than batch use? > > Stitching will still work without the GUI - though I think hugin_executor > does depend on wxwidgets even though it doesn't use a display. > > There is also pto2mk2 in Panotools::Script which is more or less a drop-in > replacement for pto2mk, this isn't going away - I might even rename this to > pto2mk so old scripts carry on working. > > > Great! I used the mk file for another program I wrote to spread the different stages across computers on my network, so as long pto2mk2 still does the same thing I'll be set.
Thanks, Kevin -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/80dafd33-29e1-443d-9c89-52f63ddc41e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
