Hi Frederic,

Am Dienstag, 5. November 2013 10:41:19 UTC+1 schrieb Frederic Da Vitoria:
>
> OK, I'll refrain from advising this from now on. But you realize that 
> similar problems have been going on for several months (more than a year?), 
> that it generates frustrated Windows users (I have a hunch this is a 
> Windows-specific issue) and that in the Windows world, the general user 
> behavior is: "if the software doesn't work, then use another one"? Windows 
> users who know what a bug tracker is (I am not even saying "who know how to 
> use a bug tracker") are few. So that letting users get hit by PTBatcherGUI 
> problems might achieve getting less Hugin users instead of solving the 
> PTBatcherGUI issue.
>
> It would be nice if all would always works.
There is always a conflict between adding new features (with maybe new 
bugs) and rock-solid stability. If you prefer always rock-solid stability, 
we can not add new features, because we have not the man power to test them 
before release to this extent.
So in the scope of our little project with hobby people we need the 
feedback from the user (with a wide variety of systems and wide variety of 
use case, not to mention the big variety of image format..) to fix the 
issues and make it more stable. So features can become more stable with 
time - but only when they get tested and issues reported and fixed. 

Big software team can do that testing more extensive before release - but 
they have the man power, time and money.

But here it often goes:
1.) Does not work!
2.) Try to identify the culprit and give ideas to try.

And then it ends. No feedback, no this solved it or so. So we can not fix 
the issue or make it more robust, because we don't know what goes wrong in 
specific conditions.

To use an overstressed comparison: When you car does not work correctly, do 
you then go to the garage and say simply  "The car does not work 
correctly."? Yes, then you have a very fine garage. But I think in most 
case they ask you, what exactly does not work and try to isolate the 
failure.

But here it gets expected that all should work in all user cases on all 
machines around the world with all different images, and this in the first 
run.

Thomas

Thomas

-- 
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/264246e3-a10b-4d77-a294-094cfbe33841%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to