Re: [hugin-ptx] Hugin 2018.0 rc2 released

2018-01-27 Thread Greg 'groggy' Lehey 
On Saturday, 27 January 2018 at  0:03:44 -0800, T. Modes wrote:
> Hi all,
>
> because of a found bug we are releasing release candidate 2 of Hugin
> 2018.0.

The bug with "in-source builds are not allowed" is still there.  Apart
from that it builds under FreeBSD.  It would be nice to finally get
this fixed.

Greg
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

-- 
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/20180127233223.GA74795%40eureka.lemis.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

[hugin-ptx] Re: if ... then ... Opening projects and images from Windows Explorer

2018-01-27 Thread Abrimaal 
Opinions are various. At least allowing Hugin to load projects with the big 
button will simplify the work.

How to distinguish between Open project and Merge / Add images to project:

On a blank screen, big button clicked:
- Selecting a single .pto file does NEW, Open Project
- Selecting more than one .pto files does NEW,  Open and merge projects
- Selecting a .pto file and images does NEW, Open project, add images to 
project
- Selecting images only may Add images as it works currently or do NEW, 
Open images. Decision belongs to you. 

While work, selection from menu:
Selecting from menu File/Add (not using the big button) will not do New, 
but it will allow to add images and projects to the currently open project.



On Saturday, January 27, 2018 at 9:11:15 AM UTC+1, T. Modes wrote:
>
>
>
> Am Samstag, 27. Januar 2018 07:03:48 UTC+1 schrieb Abrimaal:
>>
>> When we click [ Add Images ] button in the simple interface, we can see 
>> both images and .pto projects,
>> but we cannot open a project from here, because an error "Could not 
>> decode image" is displayed. (attachment 1)
>>
>> When we want to open an existing project from the menu [ Open ], you 
>> don't see what you open, because images are not displayed. (attachment 2)
>> (let's assume that images and projects are in the same folder)
>>
> If Hugin displays .pto projects in Add images, why not to open projects 
>> from here and rename the button to [ Open files ] or [ Load files ]
>> It looks simple to detect the header '# hugin project file' and jump to 
>> project opening routine. At least simple compared to all calculations 
>> performed by Hugin :)
>>
>
> This happens only because you set the file filter in the add images dialog 
> to "all files" instead of the default "all image file". (But you didn't 
> this in the load project.)
>
> It will allow the user to start a new project, load images, open projects, 
>> add images to a project and merge projects with a single button.
>>
> How do you want then to distinguish between open project and merge 
> project? And how should a new project started in this context?
> Sorry, but this is more then confuse.
>
>

-- 
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/a245d758-6691-4fee-b135-1276f99d59f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2018.0 rc2 released

2018-01-27 Thread Bruno Postle 

On Sat 27-Jan-2018 at 00:03 -0800, Thomas Modes wrote:


because of a found bug we are releasing release candidate 2 of Hugin
2018.0.


As usual, Fedora packages can be found in 'copr': 
https://copr.fedorainfracloud.org/coprs/bpostle/panorama/

--
Bruno

--
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/20180127120108.GA5593%40postle.net.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin 2018.0 rc2 released

2018-01-27 Thread Niklas Mischkulnig 
The executables for macOS (10.9 and newer) are available for download from 
sourceforge:
https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/Hugin-2018.0.0-rc2.dmg/download

sha1: 1410138b91b25c9a6290536eaef330a07a912099  Hugin-2018.0.0-rc2.dmg


Am Samstag, 27. Januar 2018 09:03:44 UTC+1 schrieb T. Modes:
>
> Hi all,
>
> because of a found bug we are releasing release candidate 2 of Hugin 
> 2018.0. 
>
> Source tarball can be downloaded
> at sourceforge: 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/hugin-2018.0rc2.tar.bz2/download
> or at launchpad: 
> https://launchpad.net/hugin/2018.0/2018.0rc2/+download/hugin-2018.0rc2.tar.bz2
>
> Verify its checksums:
> md5:91cb2c31409c9ef02fc86e17ec2fa068  hugin-2018.0rc2.tar.bz2
> sha1: 
> bf62cc597015f8fcbddb52590fe3f8eac497449f  hugin-2018.0rc2.tar.bz2
>
>
> This is a source code release. 
> Users communities produce executables for their respective platforms. 
> Please announce them here.
>
> (The rc2 corresponds to changeset 5abfb4de7961 in our repository, which is 
> also tagged as 2018.0rc2).
>
> Changes since 2018.0 rc1
> * Fixes crash when closing Hugin with open help window (Mac).
> * Check window help position before opening (to prevent help window 
> opening outside of desktop area).
> * Fixes a warning in lens_calibration_gui
>
> Changes since 2017.0
>
> The version 2018.0 is mainly a bug fix release and introduce some minor 
> new features.
> * Several improvements for optimizer tabs:
>**mark deselected images
>** allow changing optimizer variables for all selected images at once
>** option to ignore line cp
> * hugin_stacker: New tool to stack overlapping images with several 
> averaging modes (e.g. mean, median).
> * Hugin: Added option to disable auto-rotation of images in control point 
> and mask editor.
> * Nona, verdandi and hugin_stacker can now write BigTIFF images (for files 
> >4 GB). The output of BigTIFF has to manually activated on the command 
> line. It is not set automatically. (For a complete panorama in BigTIFF you 
> will probably also need enblend/enfuse from repository. The last released 
> version of enblend does not yet support writing BigTIFF files.)
> * Added expression parser to GUI: This allows to manipulate several image 
> variables at once. (This is the same as running pto_var --set from the 
> command line.) This can be used e.g. to prealign the images in a given 
> setup and then run cpfind --prealigned to search control points only in 
> overlapping images.
> * Add user-defined assistant and expose it in the GUI. It allows to set up 
> different assistant strategies without the need to recompiling. Provide 
> also some examples (scanned images, multi-row panoramas with orphaned 
> images, single-shot panorama cameras).
>
> Upgrading from previous versions of Hugin should be seamless. If you do 
> have problems with old settings, these can be reset in the Preferences 
> window by clicking 'Load defaults'.
>
> The release notes can be found at 
> http://hugin.sourceforge.net/releases/2018.0.0/en.shtml 
>
> Please test and report bug/issues to mailing list or bug tracker 
> https://bugs.launchpad.net/hugin
>
> Know issue
>
> Hugin does not run native on Wayland because of a bug in the underlying 
> wxWidgets library.
>
> The source code contains a workaround which forces the usage of the 
> XWayland emulation layer. This workaround has be activated during compiling 
> by adding -DUSE_GDKBACKEND_X11=on to the CMake command line. 
>

-- 
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/92145fe9-8d72-494f-86f5-43d053641df5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: if ... then ... Opening projects and images from Windows Explorer

2018-01-27 Thread T. Modes 


Am Samstag, 27. Januar 2018 07:03:48 UTC+1 schrieb Abrimaal:
>
> When we click [ Add Images ] button in the simple interface, we can see 
> both images and .pto projects,
> but we cannot open a project from here, because an error "Could not decode 
> image" is displayed. (attachment 1)
>
> When we want to open an existing project from the menu [ Open ], you don't 
> see what you open, because images are not displayed. (attachment 2)
> (let's assume that images and projects are in the same folder)
>
If Hugin displays .pto projects in Add images, why not to open projects 
> from here and rename the button to [ Open files ] or [ Load files ]
> It looks simple to detect the header '# hugin project file' and jump to 
> project opening routine. At least simple compared to all calculations 
> performed by Hugin :)
>

This happens only because you set the file filter in the add images dialog 
to "all files" instead of the default "all image file". (But you didn't 
this in the load project.)

It will allow the user to start a new project, load images, open projects, 
> add images to a project and merge projects with a single button.
>
How do you want then to distinguish between open project and merge project? 
And how should a new project started in this context?
Sorry, but this is more then confuse.

-- 
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/aa34ad8a-7897-491a-8fb4-fa0c51666a16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] if ... then ... Opening projects and images from Windows Explorer

2018-01-27 Thread Gunter Königsmann 
As an ordinary user I am happy with the nee button.
Also I expect the "open" button to offer to open project files by default.
Which it currently does. But if the filter of the open dialogue it opens
could be changed to "image files" I wouldn't be unhappy about that.

Am 27.01.2018 8:01 vorm. schrieb "David W. Jones" :

> On 01/26/2018 08:03 PM, Abrimaal wrote:
>
> Hmm, first disclaimers:
>
> 1. I use Linux.
> 2. I don't use the Simple Interface.
> 3. I rarely add images to an existing PTO. If I have a folder of images to
> include in a project, I select them all and right-click to open in Hugin
> PTO Generator.
>
> When we click [ Add Images ] button in the simple interface, we can see
>> both images and .pto projects,
>> but we cannot open a project from here, because an error "Could not
>> decode image" is displayed. (attachment 1)
>>
>
> Why would you want to open a project from an "Add Images" button? A
> project isn't an image.
>
> When we want to open an existing project from the menu [ Open ], you don't
>> see what you open, because images are not displayed. (attachment 2)
>> (let's assume that images and projects are in the same folder)
>>
>
> But what image is the one to show for the project in the file open window?
> Isn't the operating system responsible for generating and displaying
> thumbnails of images in "open file/image" dialogs? How could it generate
> the appropriate thumbnail image without loading and rendering the project,
> or assuming that whatever image there is in the folder that has the same
> name as the project is the project output, and thumbnail it?
>
> If Hugin displays .pto projects in Add images,
>>
>
> It shouldn't. I'd expect the button to open a project would only see PTO
> files while the one to add images would only see image files.
>
> why not to open projects from here and rename the button to [ Open files ]
>> or [ Load files ]
>>
>
> Confusing - label doesn't indicate the specific function.
>
> It looks simple to detect the header '# hugin project file' and jump to
>> project opening routine. At least simple compared to all calculations
>> performed by Hugin :)
>>
>> Additionally, we could select a project file and images, what will open a
>> project and add images to it.
>>
>
> Dragging and dropping images into an open Hugin project adds them to it.
>
> Programmatically - if I drag a PTO and images into an existing project
> window ... I guess Hugin would have to merge the PTOs first, then add the
> images? Anyway, in what order does the OS offer the dropped files to the
> receiving program?
>
> We could select two or more .pto files to merge projects.
>>
>
> I just tried dropping 2 PTO files into an open Hugin window. Nothing
> happened.
>
> Being able to merge projects by dragging one into an open Hugin project
> window - maybe it could just transparently run pto_merge behind the scenes?
> - might be useful for someone but I can't think of a reason to merge
> projects?
>
> This is not all. When we make panoramas or straighten photos one after
>> one, clicking on [ File / New ] may extend to long hours when we have many
>> files to process.
>> This button can be renamed to [ Start ]
>>
>
> No. Just no. So you spend 'long hours' clicking [Start]. Or do you want to
> be able to work on a project in the foreground while background processes
> in Hugin proceed to merge PTOs, add images, etc?
>
> It will allow the user to start a new project, load images, open projects,
>> add images to a project and merge projects with a single button.
>>
>
> Sorry, I prefer buttons clearly labeled with their functions. Makes it
> much easier to find the function I'm looking for.
>
> But what if we want to add more images to an open project? We can select [
>> Add Images ] from the menu. This is an operation that we do usually by
>> mistake, when we don't select all images we want to open. Whatever, we
>> don't do it as frequently as starting a new project (make a new panorama or
>> straighten a photo).
>>
>
> So what does that have to do with your Start button idea?
>
> What is your opinion, users and developers?
>>
>
> Interspersed above. Again, I don't use the Simple Interface, so keep that
> in mind.
>
> --
> David W. Jones
> gnomeno...@gmail.com
> wandering the landscape of god
> http://dancingtreefrog.com
>
> --
> 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/ms
> gid/hugin-ptx/49bfe0b1-5884-40f6-d59b-d239f49def5b%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ

[hugin-ptx] Re: Hugin 2018.0 rc2 released

2018-01-27 Thread T. Modes 
For Windows user: an installer package for Windows 64 bit can be downloaded 
from
https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/Hugin-2018.0rc2-win64.msi/download

MD5 checksum is
bef26239f194bd2225e7e0865bbfe47b  Hugin-2018.0rc2-win64.msi

-- 
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/12d64f29-331a-4563-bcac-3cde9cb4e03c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Hugin 2018.0 rc2 released

2018-01-27 Thread T. Modes 
Hi all,

because of a found bug we are releasing release candidate 2 of Hugin 
2018.0. 

Source tarball can be downloaded
at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/hugin-2018.0rc2.tar.bz2/download
or at launchpad: 
https://launchpad.net/hugin/2018.0/2018.0rc2/+download/hugin-2018.0rc2.tar.bz2

Verify its checksums:
md5:91cb2c31409c9ef02fc86e17ec2fa068  hugin-2018.0rc2.tar.bz2
sha1: 
bf62cc597015f8fcbddb52590fe3f8eac497449f  hugin-2018.0rc2.tar.bz2


This is a source code release. 
Users communities produce executables for their respective platforms. 
Please announce them here.

(The rc2 corresponds to changeset 5abfb4de7961 in our repository, which is 
also tagged as 2018.0rc2).

Changes since 2018.0 rc1
* Fixes crash when closing Hugin with open help window (Mac).
* Check window help position before opening (to prevent help window opening 
outside of desktop area).
* Fixes a warning in lens_calibration_gui

Changes since 2017.0

The version 2018.0 is mainly a bug fix release and introduce some minor new 
features.
* Several improvements for optimizer tabs:
   **mark deselected images
   ** allow changing optimizer variables for all selected images at once
   ** option to ignore line cp
* hugin_stacker: New tool to stack overlapping images with several 
averaging modes (e.g. mean, median).
* Hugin: Added option to disable auto-rotation of images in control point 
and mask editor.
* Nona, verdandi and hugin_stacker can now write BigTIFF images (for files 
>4 GB). The output of BigTIFF has to manually activated on the command 
line. It is not set automatically. (For a complete panorama in BigTIFF you 
will probably also need enblend/enfuse from repository. The last released 
version of enblend does not yet support writing BigTIFF files.)
* Added expression parser to GUI: This allows to manipulate several image 
variables at once. (This is the same as running pto_var --set from the 
command line.) This can be used e.g. to prealign the images in a given 
setup and then run cpfind --prealigned to search control points only in 
overlapping images.
* Add user-defined assistant and expose it in the GUI. It allows to set up 
different assistant strategies without the need to recompiling. Provide 
also some examples (scanned images, multi-row panoramas with orphaned 
images, single-shot panorama cameras).

Upgrading from previous versions of Hugin should be seamless. If you do 
have problems with old settings, these can be reset in the Preferences 
window by clicking 'Load defaults'.

The release notes can be found at 
http://hugin.sourceforge.net/releases/2018.0.0/en.shtml 

Please test and report bug/issues to mailing list or bug tracker 
https://bugs.launchpad.net/hugin

Know issue

Hugin does not run native on Wayland because of a bug in the underlying 
wxWidgets library.

The source code contains a workaround which forces the usage of the 
XWayland emulation layer. This workaround has be activated during compiling 
by adding -DUSE_GDKBACKEND_X11=on to the CMake command line. 

-- 
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/9f218aaf-b907-4309-808a-8895cffaea6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.