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

Bug 364322

Summary:	DirtyStateEditorSupport descriptionsChanged should not ignore event
Product:	[Modeling] TMF	Reporter:	Mark Christiaens <mark.g.j.christiaens>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	mark.g.j.christiaens, sebastian.zarnekow, sven.efftinge
Version:	2.1.0	Flags:	sebastian.zarnekow: juno+
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Mark Christiaens

2011-11-21 08:22:03 EST

Build Identifier: 20110916-0149 

I have a scope provider that relies on the global scope to find some declarations, even some in the same resource.  I find that an open editor is not always correctly marked up.  The reason seems to be that in an open editor, new resource descriptions are calculated and installed after every modification.  After that, a change event is propogated and eventually ends up in descriptionsChanged.  There, the event is ignored because the resources of the editor equal those of the propagated event.  

I'm not sure but I think that the for loop in descriptionsChanged should not be there?

Reproducible: Always

Comment 1 Sebastian Zarnekow

2011-11-22 07:02:02 EST

A reproducable testcase would be great.