Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364322 - DirtyStateEditorSupport descriptionsChanged should not ignore event
Summary: DirtyStateEditorSupport descriptionsChanged should not ignore event
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.1.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-21 08:22 EST by Mark Christiaens CLA
Modified: 2011-12-01 05:50 EST (History)
3 users (show)

See Also:
sebastian.zarnekow: juno+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Christiaens CLA 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 CLA 2011-11-22 07:02:02 EST 
A reproducable testcase would be great.