Am 04.11.2011 10:37, schrieb Jörn Kottmann:
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?
The communitaction between the explanation views now works only with the
selection mechanism. I think a selection event should do the trick here.
The main view (Applied Rules) is a listener and the other views are only
updated due to its selection events.
We have the same issue in the Edit View, there setInput(null) should
be called after the cas changed on the
viewer.
I'll do the changes (new listener and stuff) today in the afternoon and
try to remember to include the setInput(null)
Peter
--
---------------------------------------------------------------------
Dipl.-Inf. Peter Klügl
Universität Würzburg Tel.: +49-(0)931-31-86741
Am Hubland Fax.: +49-(0)931-31-86732
97074 Würzburg mail: [email protected]
http://www.is.informatik.uni-wuerzburg.de/en/staff/kluegl_peter/
---------------------------------------------------------------------
