apollo.editor
Class AnnotSessionDoneEvent

java.lang.Object
  java.util.EventObject
      apollo.editor.FeatureChangeEvent
          apollo.editor.AnnotationChangeEvent
              apollo.editor.AnnotSessionDoneEvent

All Implemented Interfaces:

java.io.Serializable

public class AnnotSessionDoneEvent
extends AnnotationChangeEvent

This event indicates that the editor is done with a series of edits. The view uses this as a signal to resynch and redraw itself.

See Also:

Serialized Form

Field Summary

Fields inherited from class apollo.editor.FeatureChangeEvent

ADD, DELETE, logger, MERGE, parentFeature, REDRAW, REPLACE, SPLIT, SYNC

Fields inherited from class java.util.EventObject

source

Constructor Summary

AnnotSessionDoneEvent(java.lang.Object source)
do we need annot top or changed feature?

Method Summary

boolean

isEndOfEditSession() once compound transactions are fully in place i think this can be phased out essentially this can be seen as a hack around a lack of compound transactions.

Methods inherited from class apollo.editor.AnnotationChangeEvent

addTransaction, getAnnotTop, getChangedAnnot, getChangeTop, getChildChangeEvent, getDeletedFeature, getNumberOfChildren, getOldComment, getOldId, getOldString, getParentFeature, getSubpartRank, isCommentChange, isStringChange, isUndo, setDeletedFeature, setOldComment, setOldId, setOldString, setSubpartRank, toString

Methods inherited from class apollo.editor.FeatureChangeEvent

getAddedFeature, getChangedFeature, getOperation, getOperationAsString, getReplacedFeature, getSource, getSubpart, getUpdateDetails, hasSubpart, isAdd, isCompound, isDelete, isExonChange, isMerge, isMove, isRootAnnotChange, isSplit, isSync, isTranscriptChange, isUpdate, setChangeTop, setParentFeature, setReplacedFeature

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

AnnotSessionDoneEvent

public AnnotSessionDoneEvent(java.lang.Object source)

do we need annot top or changed feature?

Method Detail

isEndOfEditSession

public boolean isEndOfEditSession()

Description copied from class: FeatureChangeEvent

once compound transactions are fully in place i think this can be phased out essentially this can be seen as a hack around a lack of compound transactions.

Overrides:

isEndOfEditSession in class FeatureChangeEvent