Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "FAQ How can I be notified on property changes on a resource?"
m |
|||
| Line 1: | Line 1: | ||
| − | It depends what you mean by ''properties''. For some metadata stored on resources, | + | It depends what you mean by ''properties''. For some metadata stored on resources, such as markers and sync info, an <tt>IResourceChangeListener</tt> can be used to be notified when they change. Other metadata, such as session and persistent properties, has no corresponding change notification. This is a design trade-off, as tracking and broadcasting change notifications can be quite expensive. Session and persistent properties are designed to be used only by the plug-in that declared the property, so other plug-ins should never be tracking or changing properties declared by your plug-in. |
| − | such as markers and sync info, an <tt>IResourceChangeListener</tt> can be | + | |
| − | used to be notified when they change. Other metadata, such as session and | + | |
| − | persistent properties, has no corresponding change notification. This is a design | + | |
| − | trade-off, as tracking and broadcasting change notifications can be | + | |
| − | quite expensive. Session and persistent properties are designed to be used only | + | |
| − | by the plug-in that declared the property, so other plug-ins should never be | + | |
| − | tracking or changing properties declared by your plug-in. | + | |
| − | + | ||
== See Also: == | == See Also: == | ||
| − | + | *[[FAQ_How_can_I_be_notified_of_changes_to_the_workspace%3F]] | |
| − | [[FAQ_How_can_I_be_notified_of_changes_to_the_workspace%3F]] | + | *[[FAQ_How_do_I_store_extra_properties_on_a_resource%3F]] |
| − | + | *[[FAQ_How_can_I_be_notified_when_the_workspace_is_being_saved%3F]] | |
| − | [[FAQ_How_do_I_store_extra_properties_on_a_resource%3F]] | + | *[[FAQ_How_do_I_react_to_changes_in_source_files%3F]] |
| − | + | ||
| − | [[FAQ_How_can_I_be_notified_when_the_workspace_is_being_saved%3F]] | + | |
| − | + | ||
| − | [[FAQ_How_do_I_react_to_changes_in_source_files%3F]] | + | |
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | <hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | ||
Latest revision as of 22:18, 29 May 2006
It depends what you mean by properties. For some metadata stored on resources, such as markers and sync info, an IResourceChangeListener can be used to be notified when they change. Other metadata, such as session and persistent properties, has no corresponding change notification. This is a design trade-off, as tracking and broadcasting change notifications can be quite expensive. Session and persistent properties are designed to be used only by the plug-in that declared the property, so other plug-ins should never be tracking or changing properties declared by your plug-in.
See Also:
- FAQ_How_can_I_be_notified_of_changes_to_the_workspace?
- FAQ_How_do_I_store_extra_properties_on_a_resource?
- FAQ_How_can_I_be_notified_when_the_workspace_is_being_saved?
- FAQ_How_do_I_react_to_changes_in_source_files?
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.