On 11/4/11 10:28 AM, Peter Klügl wrote:
Yes, but I do not use the CAS or CasDocument as input in my views for some reasons. In some explanation views the input is set by a different view and that input is only a subtree of some own representation. I would provide both documents in the interface and then only call setInput with the new one in the views that actively use the inputChanged method.
The explanation views need to be cleared when the CAS changes right? I actually wonder how this is usually be handled in eclipse. To synchronize the explanation view I would use eclipse selection mechanism. But how do I clear it then? Sending out an empty selection event or should the view list for CAS changes and then clear itself?
We have the same issue in the Edit View, there setInput(null) should be called after the cas changed on the
viewer. Jörn
