| Summary: | DCR - Callbacks to notice file changes | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kevin Haaland <Kevin_Haaland> |
| Component: | Resources | Assignee: | DJ Houghton <dj.houghton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bvukojevic |
| Version: | 2.0 | Keywords: | usability |
| Target Milestone: | 3.0 M8 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Kevin Haaland
PRODUCT VERSION: Build 118 - jdk - winNT Moving to Core for comment on the first item (not noticing file changes). As far as I can tell from the scenerio below once the file has been opened initially in the editor, the filesystem is not consulted until the editor is re- activated. At that point in time we do notice a change in the file on the filesystem and report that problem. Callbacks from the filesystem are not supported so we cannot agressively report filesystem changes to the user. Moving to Platform/UI for comment/closure on 2nd problem. UI would need to have Core callback to detect the file is out of sync. Please put this defect report in your "Resolve Later" category. It's not a UI problem. Filesystem callbacks are not part of the 2.0 plan. Moving to Resolved/LATER. Re-opening to close. We have integrated the optional auto-refresh plug-in into the Eclipse SDK and it is now a part of the regular downloads. As of the M8 build it can be configured via: Window -> Preferences -> Workbench -> Work in Progress The win32 implementation uses file-system callbacks for notification. The linux implementation uses FAM. All other platforms use a polling mechanism. Marking as FIXED. |