Bug 89672 - default value for refreshing workspace automatically
Summary: default value for refreshing workspace automatically
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 69007 242718 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-30 15:09 EST by Jim des Rivieres CLA
Modified: 2008-08-07 16:16 EDT (History)
3 users (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 Jim des Rivieres CLA 2005-03-30 15:09:42 EST 
Build I20050330-0500

The default value for the pref for refreshing the workspace automatically 
defaults to off.

It would seems reasonable for it to default to on. Is there any reason that 
this cannot be done?
Comment 1 John Arthorne CLA 2005-03-30 16:09:27 EST 
It's core team's lonely stand against turning on all the expensive bells and
whistles by default <g>

Autorefresh necessarily consumes CPU as it searches for external changes. On
windows, every time a file in the workspace is modified, a native callback
notifies us and we do background work to determine if the file needs refreshing
(even if it was changed from within Eclipse).  On non-windows platforms, a
background polling thread churns away searching for changes.  The net effect is
that it will keep using CPU, and for the large group of users who never modify
their workspace using external tools, this effort is entirely wasted.  Only
users that want the feature should pay the performance hit for it.  It really
comes down to the question of what percentage of the user community actually
uses this - I still don't have a feel for the answer to that question.
Comment 2 John Arthorne CLA 2005-04-13 16:57:24 EDT 
Closing.  No plans to change the default.
Comment 3 Billy Biggs CLA 2005-06-21 09:38:08 EDT 
*** Bug 69007 has been marked as a duplicate of this bug. ***
Comment 4 John Arthorne CLA 2008-08-07 16:16:35 EDT 
*** Bug 242718 has been marked as a duplicate of this bug. ***