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
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com