"Irving, Dave" <dave.irving@logicacmg.com> wrote on 04/10/2006 12:30:59
PM:
> > Then I did a right click, "Refresh" on the project - which took 5mins
> > (with NO progress information other than "0%" progress until it
> > completed).
>
> Just to clarify, the next refresh performed after a switch of my project
> root directory is the refresh which takes a very long time. It does not
> matter whether this refresh occurs automatically (i.e, invoked by
> SwitchToUrlCommand), or manually (i.e, with my changed
> SwitchToUrlCommand, and a manual "refresh" after the switch).
> Also, in both scenarios, the refresh has a dodgy progress monitor: No
> progress is recorded until everything completes - it just sits on
> "Building Workspace 0%" until it finally completes (not what ordinarily
> happens with a "normal refresh").
That behavior is usually what happens when the Build workspace process is
waiting for something else. Typically, this would be Subclipse refreshing
its status cache.
> Finally, this occurs even if no version controlled files are altered as
> a result of the switch (although meta-data files will of course be
> changed).
Given that all of the .svn metadata will have been updated it would be
normal for this to trigger Subclipse to refresh its cache.
This is making me wonder if this isn't a catch-22. If you fix the
underlying problem that caused us to add the Refresh code, it is still
going to be a slow process because all that will happen is that the
refresh will be performed automatically.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Mon Apr 10 19:09:38 2006