| Summary: | [PropertiesView] [Views] Pinned property view shows deleted resource | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Eric Moffatt <emoffatt> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | bokowski, daniel_megert, pwebster, rakes123, remy.suen, rolf.theunissen |
| Version: | 3.5 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Eric Moffatt
Just tried this with the EMF ecore editor and you can change the properties. This isn't really a valid test though since the EMF editor maintains a reference to the 'deleted' object in its undo stack... Likely means that this is 'safe' for GEF/GMF as well (for the same reasons). Does anybody know of an editor that *really deletes* an object and is a property provider? *** Bug 393831 has been marked as a duplicate of this bug. *** The properties view is not so much 'pinned' against a particular resource, it is pinned against the last selection it received from a part. This selection will not change by removing a resource. The selection is adapted to a IPropertySource, and in case of a selected IFile that is a FilePropertySource. The FilePropertySource is not monitoring the IFile, so there is no way that the properties view is notified of changes. Even if FilePropertySource would monitor the file, I am not sure how to update the properties view, but that should be possible as I have seen two property views in sync when one of them is edited. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |