Description Rodrigo Peretti 2001-10-10 22:25:21 EDT

- click on a project in the navigator -> Catchup
	- the project is a java project and contains changes in only one package
	- all the changes are conflicts so I'd like to go through them one by one
	- the project tree starts all collapsed so I have to expand folder by folder until
		I get to the desired level
	- click on the first class and analise conflicts
	- right click -> Catchup
	- the project gets collapsed again so I have to expand again to the desired folder

	Suggestion:
	- the Catchup/Release tree could show up expanded to the first folder (inclusive) that
		contains changes
	- the selection should appear in the folder and not in the first file (because the
		compare is too slow)

NOTES:

RTP (5/16/01 4:48:05 PM)
	Note that this behaviour is achieved if the conflicing class is changed manually (editing
it in the left text area or using the copy changes options) and them clicking on the "select
next change" arrow in the structure compare.

KM (5/17/01 10:36:20 AM)
	Suggestion #1 is duplicate PR.
	Suggestion #2 is a PR against Compare since it should not be as slow as it is.  Moving to UI.

AW (28.05.01 10:07:34)
	The time to compare to resources is dominated by the time to fetch the resource from the repository.
	Seems to be a VCM issue.