This change in the AnnotationEditor:
protected void doSetInput(IEditorInput input) throws CoreException {
ICasDocument oldDocument = getDocument();
super.doSetInput(input);
ICasDocument newDocument = getDocument();
fireCasDocumentChanged(oldDocument, newDocument);
This code could sent null for the old or new document. We should
maybe mention that in the listener interface. If a document is opened
where the type system cannot be found for the new document will be null.
Jörn
On 11/4/11 2:55 PM, Peter Klügl wrote:
Am 04.11.2011 14:52, schrieb Jörn Kottmann:
On 11/4/11 2:50 PM, Peter Klügl wrote:
You are of course correct. My use case would be: You opened a cas
with the editor and a type system. Then the file is replaced with a
CAS built on a different type system. The editor should of course
create a new cas with the other type system.
Yes, but this is covered by the CAS change support you are currently
working on.
Jörn
Ah ok. I only thought because you mentioned that the type system
cannot change for the view...
Peter
