phenote.edit
Class EditManager
java.lang.Object
phenote.edit.EditManager
public class EditManager
- extends java.lang.Object
The way editing works is gui makes update transaction (see CharFieldGui and
AutoComboBox) and calls
EditManager.updateModel(), EM calls UpdateTrans constructs CharFieldValues and calls
CVF.editModel which call charFieldEnum.setValue which calls the appropriate
method in CharacterI. EM also shoots out char change event to its listeners
UpdateTrans takes Strings(for free text) or OBOClasses(ontologies).
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
EditManager
public EditManager(CharacterListManager clManager)
getDeletedAnnotations
public java.util.List<CharacterI> getDeletedAnnotations()
inst
public static EditManager inst()
reset
public static void reset()
getEditManager
public static EditManager getEditManager(java.lang.String group)
addCharChangeListener
public void addCharChangeListener(CharChangeListener l)
removeCharChangeListener
public void removeCharChangeListener(CharChangeListener l)
undo
public void undo()
getCurrentTransaction
public TransactionI getCurrentTransaction()
getTransactionList
public java.util.List<TransactionI> getTransactionList()
updateModel
public void updateModel(java.lang.Object src,
TransactionI ct)
deleteFromValList
public void deleteFromValList(java.lang.Object src,
CharacterI c,
CharField cf,
CharFieldValue kidToDelete)
addInitialCharacter
public void addInitialCharacter()
- The initial blank character is a fundamental undoable state, so dont
keep the transaction for this as its not undoable
addNewCharacter
public void addNewCharacter()
- same as addInitialChar except we record the adding in the transaction list
as it can be undone
addCharacter
public void addCharacter(CharacterI c)
copyChars
public void copyChars(java.util.List<CharacterI> charsToCopy)
deleteChars
public void deleteChars(java.util.List<CharacterI> delChars)