[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
>But this DOES NOT turn a PTO magically into an image, so it cannot be opened as an image, because it isn't an image. Yes, I know. I use Load images button to preview how the panorama looks. (right click -> open in a default viewer) The .pto file is saved just before the panorama in the same folder. If the panorama requires corrections, then right click .pto -> Send to -> Hugin. Now it became impossible. When there are a few hundreds partial images in a folder, it is not easy to find the proper .pto file from the standard menu File -> Open. On Monday, February 25, 2019 at 10:51:32 PM UTC+1, Bart van Andel wrote: > > Abrimaal wrote: >> >> It does not work in the 2019 beta 2 version, because the filter "All >> files" has been changed to "All images". >> > > Sorry, apparently I missed this. BTW I think 2018 version had both > > >> I typed: >> * >> "*" >> *.* >> "*.*" >> in the filename field. >> .pto files are among the images, but not accessible. >> > > Just * works for me to show all files. But this DOES NOT turn a PTO > magically into an image, so it cannot be opened as an image, because it > isn't an image. > -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ea7223fa-859d-44f1-b449-803fc1bb2211%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
Abrimaal wrote: > > It does not work in the 2019 beta 2 version, because the filter "All > files" has been changed to "All images". > Sorry, apparently I missed this. BTW I think 2018 version had both > I typed: > * > "*" > *.* > "*.*" > in the filename field. > .pto files are among the images, but not accessible. > Just * works for me to show all files. But this DOES NOT turn a PTO magically into an image, so it cannot be opened as an image, because it isn't an image. -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/774bf62d-23b5-4b67-bbdd-c82d74a48161%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
[image: file-filter-all-images-instead-of-all-files-pto-not-accessible.png] On Monday, February 25, 2019 at 6:06:29 PM UTC+1, Bart van Andel wrote: > > All the things you want are basically the job of a file manager. It isn't > reasonable to assume that all tools should be able to perform file manager > things. If you have images with a wrong extension, rename them. > > Having said that, if you want to show all files in any regular "Open File" > or "Save File" dialog in Windows, you can usually just enter "*" in the > "File name" field and hit enter. Just verified, this works in Hugin too. > Actually the drop down to the right of this file field already contains an > option for showing "All files (*)", both in Hugin 2018.0.0 and the current > 2019.0.0. I think we can conclude you've been served already a while ago ;-) > > On Thursday, 21 February 2019 17:56:51 UTC+1, Abrimaal wrote: >> >> Please at least allow to display All files in the Load images window. >> This way panoramas that must be quickly corrected can be sent to another >> instance of Hugin >> Right click .pto file -> Send to -> Hugin. >> >> Btw. filtering images by extension is not the best method, it excludes >> images without extension, or with extensions such as .jpg.bk >> that could be created in mobile apps or other systems, and they are >> normal .jpg or .png files. >> Take a look at the file header and the file type, for .jpg this is: >> ÿØÿà JFIF >> The Windows command Findstr may be used to determine the file type. >> >> On Thursday, February 21, 2019 at 5:04:14 PM UTC+1, T. Modes wrote: >>> >>> >>> @Bart >>> Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel: What you're asking is (correct me if I'm wrong) the ability to import images from one project into another one. That is currently not supported without scripting I think. Still not the same as treating the PTO as an image though. >>> This is already possible (without scripting): in panorame editor: >>> File>Merge project >>> >> -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/76a846cc-6fa7-41c1-b3c6-cbbe660cd69f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
It does not work in the 2019 beta 2 version, because the filter "All files" has been changed to "All images". I typed: * "*" *.* "*.*" in the filename field. .pto files are among the images, but not accessible. On Monday, February 25, 2019 at 6:06:29 PM UTC+1, Bart van Andel wrote: > > All the things you want are basically the job of a file manager. It isn't > reasonable to assume that all tools should be able to perform file manager > things. If you have images with a wrong extension, rename them. > > Having said that, if you want to show all files in any regular "Open File" > or "Save File" dialog in Windows, you can usually just enter "*" in the > "File name" field and hit enter. Just verified, this works in Hugin too. > Actually the drop down to the right of this file field already contains an > option for showing "All files (*)", both in Hugin 2018.0.0 and the current > 2019.0.0. I think we can conclude you've been served already a while ago ;-) > > On Thursday, 21 February 2019 17:56:51 UTC+1, Abrimaal wrote: >> >> Please at least allow to display All files in the Load images window. >> This way panoramas that must be quickly corrected can be sent to another >> instance of Hugin >> Right click .pto file -> Send to -> Hugin. >> >> Btw. filtering images by extension is not the best method, it excludes >> images without extension, or with extensions such as .jpg.bk >> that could be created in mobile apps or other systems, and they are >> normal .jpg or .png files. >> Take a look at the file header and the file type, for .jpg this is: >> ÿØÿà JFIF >> The Windows command Findstr may be used to determine the file type. >> >> On Thursday, February 21, 2019 at 5:04:14 PM UTC+1, T. Modes wrote: >>> >>> >>> @Bart >>> Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel: What you're asking is (correct me if I'm wrong) the ability to import images from one project into another one. That is currently not supported without scripting I think. Still not the same as treating the PTO as an image though. >>> This is already possible (without scripting): in panorame editor: >>> File>Merge project >>> >> -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c5685424-cb01-4197-aa0d-dd5831064e37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Installed hugin now what?
Am 25.02.19 um 18:13 schrieb Bart van Andel: > @Abrimaal: > > Although the default installation folder in Windows is "C:\Program > Files", it is not recommended to install any third party software > on C:, except drivers, codecs, fonts and other shared files. > Files on C: are often protected by Windows in various ways, > That is one of the reasons why most applications default to be installed in there: In this directory they are at least a bit protected against being changed by malware. -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5c5ccbb5-ff0a-b9b3-f10b-b5e28dbfe528%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Installed hugin now what?
@Abrimaal: > > Although the default installation folder in Windows is "C:\Program Files", > it is not recommended to install any third party software on C:, except > drivers, codecs, fonts and other shared files. > Files on C: are often protected by Windows in various ways, > Better to install software on a different hard drive or partition. The > user can access all files, the system is more efficient and easier to > manage. > This is not generally true. "C:\Program Files\" and its 32 bit equivalent "C:\Program Files (x86)\" are perfectly valid places to install software. In fact, certain software may fail to function if you change the default location (yes, that's bad design, but still true). Hugin has been running from the default location on my machines for years and this never caused any problem. Please don't spread FUD like this. -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/de5f9fa2-27cc-451c-a08d-1d35170549db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1
> > @Bart > Am Donnerstag, 21. Februar 2019 15:52:02 UTC+1 schrieb Bart van Andel: >> >> What you're asking is (correct me if I'm wrong) the ability to import >> images from one project into another one. That is currently not supported >> without scripting I think. Still not the same as treating the PTO as an >> image though. >> > This is already possible (without scripting): in panorame editor: > File>Merge project > Thanks, didn't know! I haven't had a use for this yet though, so that may be why I never noticed. -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5141f1da-fb9b-4365-a953-6a6c6e9bc382%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
