Bug 2560 - Unexpected "Update Conflict" dialog (1GFX3JX)
Summary: Unexpected "Update Conflict" dialog (1GFX3JX)
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2001-10-10 22:38 EDT by Dani Megert CLA
Modified: 2002-03-20 16:43 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2001-10-10 22:38:47 EDT
1. Copy a Java CU to another project (X)
	2. Start editing the CU in X in the Java editor
	3. Copy the same CU again to X
	4. Choose "replace" in the dialog that pops-up
		(Note: The file in the editor is NOT replaced)
	5. Save the file that you started to edit
	==> "Update Conflict" dialog appears.

	Replace means replace to me. It is hard to understand
	why a workbench operation only acts on the file
	system but not on the workbench itself.

	Maybe the dialog could be smart and warn the user
	about the fact that the file is open in the editor and
	that the editor content will be lost.

	The user could then either go on and the tool would
	do what the user told it to do (i.e. replace) or press
	cancel and eventually save the edited file under
	another name.


NOTES:
EG (7/10/01 11:07:04 AM)
	the current behaviour is the designed and agreed upon one.
	Moving to ITPUI it is interesting user feedback.
Comment 1 DJ Houghton CLA 2001-10-29 19:00:30 EST
PRODUCT VERSION:
	0.9


Comment 2 Kevin Haaland CLA 2002-03-20 16:43:59 EST
No plans to change current 2.0 behavior