Daniel Serodio <daniel.listas@xxx.com.br> wrote on 02/23/2006 11:21:57 AM:
> Mark Phippard wrote:
> > The job of Subclipse, or any plugin, is not to explicitly refresh
anything
> > it is to send the proper notifications that the file has been changed.
The
> > Eclipse framework then takes care of the rest. We definitely send
those
> > notifications, that is why you see the decorators change.
> >
> > When I test this specific example it works correctly for me. When I
> > revert the change the decorators change and if I view the project
> > Properties the reverted settings are showing.
> >
> > The rest is up to Eclipse.
> >
> I agree, but what I don't understand is why "Refresh Automatically" is
> not selected by default. Most Eclipse (not only Subclipse) newbies get
> bitten by the need to hit Refresh.
Refresh Automatically exists for a different reason. If you work entirely
in Eclipse everything should refresh automatically by default (as long as
the plugins are well-behaved and send change notifications). This
preference exists to have Eclipse monitor your workspaces for changes that
are made outside of Eclipse. So, if you edit a file using an external
editor when you save it, Eclipse will pick up the change and notify the
change listeners. Prior to this setting you would have to do a manual
Refresh.
In general, you do not need this preference turned on as it is a fairly
heavy process and only solves a problem that you might not even have.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 23 17:53:11 2006