Bug 516248 - Toolbar button for navigating to next / previous unresolved diff missing
Summary: Toolbar button for navigating to next / previous unresolved diff missing
Status: NEW
Alias: None
Product: EMFCompare
Classification: Modeling
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: EMF Compare CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-05 09:26 EDT by Philip Langer CLA
Modified: 2018-04-19 04:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Langer CLA 2017-05-05 09:26:28 EDT
Users reported that when they deal with large comparisons, it is quite difficult to navigate through the unresolved resources, because the next/previous diff buttons only jump from diff to diff, whether or not those diffs are unresolved or merged already.

If a user is in a merging session with many diffs and he/she accepts one diff, other diffs might be accepted automatically. Now the user would like to jump to the next diff he/she has to handle, and that is an unresolved diff. However, there is no action to do that.

I suggest to add additional actions that allow navigating to the next / previous unresolved diff alongside the existing navigation buttons. Ideally, users can then configure the toolbar to decide whether they want to see both pairs of navigation buttons or only the one for navigating to unresolved or any diffs.

Also, I think we should introduce keybindings, for instance Ctrl + Shift + down / up to navigate to next / previous unresolved diff.
Comment 1 Eclipse Genie CLA 2017-05-19 10:05:00 EDT
New Gerrit change created: https://git.eclipse.org/r/97575
Comment 2 Eclipse Genie CLA 2017-06-22 07:51:58 EDT
New Gerrit change created: https://git.eclipse.org/r/96406
Comment 3 Eclipse Genie CLA 2017-09-06 12:52:36 EDT
New Gerrit change created: https://git.eclipse.org/r/104589
Comment 4 Laurent Goubet CLA 2017-09-07 10:34:40 EDT
I'd like to know how that works with the now resolved bug 518572 as that one fix should in theory fix this bug as well.