Bug 18148 - Using combinations of No and Next file button break wrapping
Summary: Using combinations of No and Next file button break wrapping
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 F2   Edit
Assignee: Erich Gamma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-29 08:35 EDT by Dean Roberts CLA
Modified: 2002-06-03 11:51 EDT (History)
0 users

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 Dean Roberts CLA 2002-05-29 08:35:57 EDT 
I20020528

Do a synchronize that has changes on at least 2 files.

1) Next through changes on 1st file.
2) When prompted about going to top say No
3) Press Next file Arrow
4) Next through changes on 2nd file notice that wrap happens with no warning.

This does not happen if you say Yes on the 1st file.
This does not happen if you say No on the 1st file but do not change files. 
(That is going through 1st file changes a 2nd time warns at the end).

I recomend that you get rid of this Prompter.
Comment 1 Erich Gamma CLA 2002-05-30 07:33:01 EDT 
should fix the problem and keep the prompter
Comment 2 Andre Weinand CLA 2002-06-01 03:33:21 EDT 
fixed for 20020601
Comment 3 Erich Gamma CLA 2002-06-02 17:50:22 EDT 
pls verify
Comment 4 Dirk Baeumer CLA 2002-06-03 11:17:54 EDT 
The current behaviour is as follows:

- you get dialog saying that end of document has been reached.
- answer no
- click next
  observe: you get to the beginning of first file also you have answered No.
  IMO you should get the dialog again.
Comment 5 Andre Weinand CLA 2002-06-03 11:51:51 EDT 
Works as designed:
In a normal workflow I would expect exactly that behavior: after having reached 
the end a dialog is posted once; after that continuing stepping doesn't ask 
again but wraps around directly.

Talked to EG and DB and decide to close bug.