Bug 2396 - Save in compare editors needs progress bar (1GEYF58)
Summary: Save in compare editors needs progress bar (1GEYF58)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P2 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Andre Weinand CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 6842 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 22:35 EDT by John Arthorne CLA
Modified: 2001-12-19 13:15 EST (History)
1 user (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 John Arthorne CLA 2001-10-10 22:35:37 EDT 
Saving a resource in compare can cause a build, so it needs a progress bar.
This should be done by compare FW, but we can do it ourselves if
that's easier.

NOTES:

KM (6/7/01 5:31:48 PM)
	Since you compare can show up outside of VCM then yes they should support.
	Moving to UI.
Comment 1 DJ Houghton CLA 2001-10-29 18:25:22 EST 
PRODUCT VERSION:

0.118
Comment 2 Andre Weinand CLA 2001-12-12 09:16:10 EST 
*** Bug 6842 has been marked as a duplicate of this bug. ***
Comment 3 Andre Weinand CLA 2001-12-19 13:15:28 EST 
The Save operation of the Compare Editor now shows progress (for milestone M1).

However in the VCM Synch View save is performed when switching between edited
files. These saves are implemented in method VCMFile.saveChanges() which is out 
of control of the Compare plugin.
VCMFile.saveChanges() should be called from a WorkspaceModifyOperation; this 
could take of the progress monitor as well.