JabRef 6.0-beta.1 · org.jabref.gui.edit.automaticfieldeditor.AutomaticFieldEditorViewModel

Field Summary

Modifier and Type	Field and Description
private final CompoundEdit	dialogEdits One step for the whole dialog: every tab records into this, and OK pushes it as a single undo entry.
private final ObservableList<AutomaticFieldEditorTab>	fieldEditorTabs
private final UndoManager	undoManager

Constructor Summary

Access	Constructor and Description
public	AutomaticFieldEditorViewModel(BibDatabase database, UndoManager undoManager, DialogService dialogService, StateManager stateManager)

Method Summary

Modifier and Type	Method and Description
public void	cancelChanges() Reverts what the tabs already wrote to the library, without recording anything.
public ObservableList<AutomaticFieldEditorTab>	getFieldEditorTabs()
public void	saveChanges()

Field Detail

dialogEdits	back to summary
private final CompoundEdit dialogEdits One step for the whole dialog: every tab records into this, and OK pushes it as a single undo entry. Named after the dialog, because that is what the user acted in.

fieldEditorTabs	back to summary
private final ObservableList<AutomaticFieldEditorTab> fieldEditorTabs

undoManager	back to summary
private final UndoManager undoManager

Constructor Detail

AutomaticFieldEditorViewModel	back to summary
public AutomaticFieldEditorViewModel(BibDatabase database, UndoManager undoManager, DialogService dialogService, StateManager stateManager)

Method Detail

cancelChanges back to summary

cancelChanges	back to summary
public void cancelChanges() Reverts what the tabs already wrote to the library, without recording anything. The one deliberate write outside the journal, and it stays outside on purpose: nothing was ever pushed — `saveChanges` is what pushes — so there is no undo step to reverse and none to add. Cancelling leaves the library where it was before the dialog opened, which is exactly the state the top of the undo stack already describes.

public void cancelChanges()

Reverts what the tabs already wrote to the library, without recording anything.

The one deliberate write outside the journal, and it stays outside on purpose: nothing was ever pushed — saveChanges is what pushes — so there is no undo step to reverse and none to add. Cancelling leaves the library where it was before the dialog opened, which is exactly the state the top of the undo stack already describes.

getFieldEditorTabs	back to summary
public ObservableList<AutomaticFieldEditorTab> getFieldEditorTabs()