hugin-devs team mailing list archive

[Yuv <679996@xxxxxxxxxxxxxxxxxx>]

On January 9, 2011 04:53:02 pm Bruno Postle wrote:
> Basically this usage of the tracker sucks.

No, we just need to fine tune our common understanding of tracker usage.


> This bug gets marked as incomplete because the bug doesn't contain
> any information

it's not a binary flag.  It may contain some information, but it is still 
incomplete to start coding.


> however the
> bugs that are marked as duplicates do contain useful and complete bug
> reports (e.g Bug #697657).

unmark bug #697657 from duplicate status and let it go the normal ticket life 
cycle.

duplicate marking has the advantage that if somebody picks up the issue, they 
will see also the related issues and may provide a solution for all of them 
together.  But if this does not work, then let those bugs that hurt enough for 
information to be complete go ahead on their own.

The next task for this ticket is still listed in comment #1.  Without that, 
there is not much that can be done about this request.


> The inevitable result will be that the
> 'duplicates' get ignored and the 'parent' bug vanishes by default.

wrong.  First of all, it takes two months of inactivity for a 'parent' bug to 
vanish.  You can set a 'cron job to ping it' every 50 days and it will not 
vanish.

simply keeping it alive and ignoring it is no better solution.

second, if you don't want it to vanish, assign it to yourself. if I am not 
mistaken, assigned bugs don't expire.  the status will still reflect the 
reality that information is missing.  But somebody will have taken 
responsibility to collect this information.

or to keep it alive and ignore it which, again, is just cosmetic and clogs the 
view from those bugs that actually attract real action.

Does the lack of keyboard shortcuts pain you? it does not pain me.  If it 
would, I would know which keyboard shortcuts that I am missing and I could 
list them out of the top of my head.

 
> It seems to me that the only way around this is to copy and paste any
> information from one bug to another when marking as duplicate, but this
> would be tedious and prone to errors.

don't do that.  just un-duplicate them (e.g. specify 'duplicate no' in an 
email to the bug) and they will go the normal ticket lifecycle again.  before 
doing that, make sure they are all tagged the same way.

Actually I am tempted to try it.  With the next email message I will:
* tag all bugs marked as duplicate of this bug with the tags 'keyboard' and 
'usability'
* unmark them as duplicate

If the system is well designed, I would expect their status to change to 'New' 
(duplicate bugs have 'Invalid' status) and they can be triaged again for 
completeness etc.

Just to back up the links, those are
    * Bug #678929
    * Bug #679831
    * Bug #679834
    * Bug #679836
    * Bug #679841
    * Bug #679900
    * Bug #679938
    * Bug #679973
    * Bug #697649
    * Bug #697657

Yuv

 tag: keyboard usability

-- 
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.