Re: [hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-03-18 Thread Abrimaal
Excellent. I always forget that I can manually modify X Y Z positions. On Monday, March 18, 2019 at 8:14:41 AM UTC+1, Bruno Postle wrote: > > > > On 17 March 2019 19:35:01 GMT, Abrimaal wrote: > > > >Creating a multiview pano is possible on a 2D screen, but except a lot of > masking, > >it

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-03-15 Thread Bart van Andel
On Thursday, 28 February 2019 14:44:52 UTC+1, Abrimaal wrote: > > "Add images" already opens Windows explorer, a second Explorer window will > only take space on the screen and it will not follow the current work > folder. The "Open file" and "Save file" look much like Windows Explorer (they

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-28 Thread Abrimaal
Theory, raw theory. When stitching 40 panoramas daily, every second counts. "Add images" already opens Windows explorer, a second Explorer window will only take space on the screen and it will not follow the current work folder. I started to write a command line script to get filenames from

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-26 Thread Bart van Andel
What prevents you from just using Windows Explorer to find your .pto between the images? I still don't see how this is Hugin's problem. You're basically "abusing" the Load Images button just to see the image previews so you can find the .pto file you want to work on, from what I gather. Didn't

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-25 Thread Abrimaal
>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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-25 Thread Bart van Andel
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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-25 Thread Abrimaal
[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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-25 Thread Abrimaal
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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-25 Thread Bart van Andel
> > @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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-21 Thread Abrimaal
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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-21 Thread T. Modes
@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

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-21 Thread Bart van Andel
This is not a bug. You're trying to load a .PTO file as if it were an image, which it is not. To take your .doc example: you can also not expect any image editor to just open a Word document because it may contain an image. Same with opening a Zip file, or any other file with some image data

[hugin-ptx] Re: Could not decode image error in 2019.0 beta 1

2019-02-15 Thread Abrimaal
*In beta2 Pre-Release 2019.0.0.75168618c648 the problem has grown.* There is no "All Files" filter in "Add Images". It means that it became impossible to right click a .pto file and open it in another instance of Hugin. "Add Images" window is the fastest method for quick preview of a finished