Bug 313699 - ResourcesPlugin.PREF_AUTO_REFRESH should exist on a per container basis, not only on as workspace wide setting
Summary: ResourcesPlugin.PREF_AUTO_REFRESH should exist on a per container basis, not ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-20 07:20 EDT by Serge Beauchamp CLA
Modified: 2019-09-06 16:15 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 Serge Beauchamp CLA 2010-05-20 07:20:37 EDT 
ResourcesPlugin.PREF_AUTO_REFRESH should exist on a per container basis, not only on as workspace wide setting
Comment 1 James Blackburn CLA 2010-05-20 07:32:03 EDT 
I think we need another preference / flag as AUTO_REFRESH is overloaded (see also bug 303517 comment 2).

The issue is that the workspace should refresh / bring into sync resources it knows to be out of date (e.g. by a file system notification hook). But the preference controlling this should be distinct from that of the expensive polling monitor.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:49 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.