Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 96838

Summary:	[PropertiesView] Add support for refreshing properties when underlying IPropertySource changes
Product:	[Eclipse Project] Platform	Reporter:	Daniel R Somerfield <dsomerfi>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	adietish, apill, bugs.eclipse.org, cernst, mv.eclipse.bugtrack, remy.suen, thatnitind
Version:	3.1	Keywords:	bugday, helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Daniel R Somerfield

2005-05-26 14:33:25 EDT

Currently, there doesn't seem to be any API for making the property window
listen to the current IPropertySource for changes. It would be nice to have an
IPropertySource.addChangeListener() or something like that so the
IPropertySource could fire a notification when an individual property changes or
the whole underlying data needs to be refreshed. The PropertyView could register
with the source and refresh the correct data.

Comment 1 Nick Edgar

2006-03-15 11:51:11 EST

Reassigning bugs in component areas that are changing ownership.

Comment 2 Nitin Dahyabhai

2006-03-15 17:08:04 EST

Can't the contributor of the IPropertySheetPage already ensure that the page is up to date on their own?

Comment 3 Aleksandr Kravets

2006-08-21 11:34:49 EDT

But isn't IPropertySheetPage is used for custom Properties View? What if I don't want to bother with creating a custom page and use default Properties View? 
Eclipse itself right now has this problem. In IDE if you right-click on any file -> Properties and change Read Only to on then Properties View will not change "editable" propery unless you click on the file that was changed.

Comment 4 Adrian

2007-09-06 09:57:21 EDT

This would solve a problem I have too. I want to load the propery source descriptors and names in a runtime Job as they're retrieved via an EJB3 call.

It would be perfect it the default PropertySheetPage registered as a listener to the IPropertySource as it would then be able to fetch details in a job and then notify the listeners.

Comment 5 Andre Dietisheim

2014-06-06 09:14:25 EDT

+1

Comment 6 Lars Vogel

2019-11-27 07:23:32 EST

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.

If the bug is still relevant, please remove the stalebug whiteboard tag.