Bug 38265 - [Sync View] Synchronize/Structure compare positions to first diff after commit.
Summary: [Sync View] Synchronize/Structure compare positions to first diff after commit.
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
: 79907 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-05-30 11:28 EDT by P Duffy CLA
Modified: 2021-10-18 13:52 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description P Duffy CLA 2003-05-30 11:28:14 EDT 
When committing individual files from the structure compare, position within 
the tree should be advanced to the next diff, not reset to the first diff, when 
a file is committed.  Stepping through the diffs and doing individual commits 
is impossibly tedious as it staands.
Comment 1 Michael Valenta CLA 2003-05-30 16:58:45 EDT 
Yes, selection management in the sync view needs work.
Comment 2 Jean-Michel Lemieux CLA 2004-06-11 16:51:45 EDT 
Post 3.0
Comment 3 Michael Valenta CLA 2006-06-15 15:24:29 EDT 
*** Bug 79907 has been marked as a duplicate of this bug. ***
Comment 4 Michael Valenta CLA 2006-06-15 15:25:13 EDT 
Bug 79907 also requests that selection be moved as well.
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:32:39 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 6 Eclipse Genie CLA 2021-10-18 13:52:25 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.