hugin-devs team mailing list archive

[Yuv <679996@xxxxxxxxxxxxxxxxxx>]

Apology for not replying on this as soon as I should have; and for the
"displeasure" caused.

First of all, an explanation of what I did with my single email.  I did
not undo your work, Thomas.  I backed it up in comment #13 - all the
bugs that were marked as duplicate are listed there.  With a single
email it could be re-done.  Then I tagged all these reports with
"keyboard" and "usability", so that if you look for those two tags, you
should get that same list (plus other relevant bugs).  Last, I
unduplicated them.

I unduplicated them, because we are still unclear about what represents
a duplicate.

If two reports say that A is missing, then they are obviously
duplicates.  But if one report says that A is missing, and another
report says that A and B are missing, then then the duplication is only
partial; and if A is more important than B, then the report saying that
A is missing should not be marked as duplicate of the report that says
that A and B are missing.

In this specific case, we have a bug saying that the whole alphabet is
missing.  If every letter of the alphabet had the same priority, then
marking them all as duplicate makes sense.  But here we have different
priorities (some missing keyboard shortcuts are very annoying while
others are a minor nuisance) and bundling them all together is the wrong
decision.  If users would perceive the whole alphabet as equally
important, they would provide the list that Bruno asked for.  Instead,
they provide a list of what is priority for them, and that's fine.  It
helps fix some of the bugs marked as duplicate, but not this overall
blanket requirement that obviously is not even important enough for the
original bug reporter to follow up on.  So let it expire; and let those
reports that get attention be fixed.

Last but not least, "expired reports".  Expired reports do not vanish.
Nothing is deleted in this system, and indeed you can find and link to
expired reports as you would to reports with every status.  Indeed it is
easier to follow a link than to use the search function which is less
than perfect.  Duplicates are automatically linked, so it is easy to
follow the links to the duplicates.  But comments links to them as well.
Comment #19 does what the duplicates list does for this specific case,
without preventing the more important bugs from this list to have a life
of their own and be addressed and fixed on a higher priority than this
bug report.  I think that marking them as duplicates is the wrong
solution; listing them as overlapping in a comment is what I would
suggest to do, and what I did in comment #13.  Let's use the duplicate
mark for real duplicates?

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679996

Title:
  Add the missing keyboard equivalents for menu items

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  Provide keyboard equivalents for most, if not all, of the top menu
  items. For example,"Fine tune all points" does not have a keyboard
  equivalent.