Home/ Questions/Q 7408037
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T05:50:19+00:00

I have an editor class which extends FormEditor class. In order to achieve save

  • 0

I have an editor class which extends FormEditor class. In order to achieve save and save As functionality for this editor, will it be enough to override:

  1. doSave(IProgressMonitor monitor)

  2. doSaveAs()

  3. isSaveAsAllowed()

these methods alone? Or anything else?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes. Please consider also the following

    • Your editor must be dirty, that means you must have called firePropertyChange(PROP_DIRTY) before
    • If you build your own RCP make sure you have added Save and Save As... Menu-Items in your ActionBarAdvisor
    • consider using the doSave Methods of the integrated FormPages (this makes sometimes more sense)
    • Do not integrate any custom user-interaction (e.g. additional dialogs) in doSave or doSaveAs methods.
    • consider providing a command-stack that the user can undo/redo modifications regarding the editors input
    • make sure to handle the fact that your editor-input can be changed in the meantime (e.g. if another editor manpulates the editors input).
    • 0