Sorry, this feels nothing like the GIMP's attempt to force users to use
their XCF format.
I've never thought of a 'project' as a single 'document' like a
wordprocessor file. So adding images to a Hugin project makes perfect
sense to me.
Now adding an image to a Word document, for instance, actually makes the
inserted image part of the document. Hugin doesn't do that at all - the
project doesn't include the image in the project file. All it has is the
image filename and Hugin-specific settings/information about the image.
So, nope, combining "Open Project" with "Add Images" still makes only
confusion.
On 01/31/2018 09:25 PM, Gunter Königsmann wrote:
That feels a bit like the gimp no more "saving" but "exporting" images
to png:
It is logical in a way. But you have to explain the logic first to every
single user. Normally if you have a word/excel/... Document "open" opens
documents and "insert" inserts images into this document.
Here the project feels like being individual images being open at the
same time so it feels like "open" would add additional ones.
If you set the filter to "all files" hugin actually tells you that,
tells how to add images to a project the canonical way and offers to do
what you actually want: to open the image files and to add them to the
project.
If I don't use hugin for a while I still keep trying to open images,
though, the first time I want to add images instead of adding them to
the project => allowing "open" to just add images would perhaps make the
program more intuitive. Hiding additional functionality here (logic that
determines automatically if the user wants to merge projects,...)
perhaps won't, though, in my personal opinion.
Am 31.01.2018 9:49 nachm. schrieb "Frederic Da Vitoria"
<[email protected] <mailto:[email protected]>>:
2018-01-31 18:00 GMT+01:00 Abrimaal <[email protected]
<mailto:[email protected]>>:
if (if ... then) failed else
Two big buttons one above the other
[ Open files ] = opens images and projects
[ Add images ] = add images to a blank or an existing project
I disagree: in a way, Hugin never "Opens" images, at least not in
the way a word processor opens a text file. The only time Hugin
opens an image is when adding it to a project. Actually, Hugin's
primary action is not to open an image, it is to add it to the
current project. So Hugin *opens* projects, and *adds* images to
projects, just as it *closes* projects and *removes* (or is it
*delete*?) images from projects. Imagine a folder containing a
project and an image with the same name, say Test_1. And now imagine
how a newbie could misunderstand what happens when opening Test_1,
if open could open the project as well as the image...
--
Frederic Da Vitoria
(davitof)
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--
David W. Jones
[email protected]
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/ababc8b9-ea60-2d63-cb20-b0d208061a5e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
