This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
EditorContextImpl in debugger listens to TopComponent.Registry and refires *all* property changes to its listeners - ActionProviders. To make it worse it uses pcs.firePropertyChange (null, null, null) so there is no chance to decide if the change is important or not. This affects startup as well as many actions in IDE - opening of editors, navigating between nodes.
I agree that this is ugly. But it's risky to change without deep knowledge how it's supposed to work.
Sure. I know :-(
And usual usecase is that listeners in turn ask EditorContext for current URL. Would it be usefull to make it part of event notification?
We now fire EditorContext property change only when the Registry event is ACTIVATED or CURRENT_NODES. We also cache the current URL, Element and EditorCookie so that they do not have to be recomputed multiple times. Hope that this is sufficient: /cvs/debuggerjpda/ant/src/org/netbeans/modules/debugger/projects/EditorContextImpl.java,v <-- EditorContextImpl.java new revision: 1.19; previous revision: 1.18
Seems to be heavily improved. I almost forgot about this class during last weeks.