public interface ISaveablesSource
IMPORTANT: As of 3.2, implementers of
satisfy the following conditions:
ISaveablePart.isSaveOnCloseNeeded()if it is dirty (the default behaviour implemented by
These conditions may be relaxed in future releases.
Additions of saveables to the list of saveables of this part are
announced using an event of type
SaveablesLifecycleEvent.POST_OPEN. Removals are announced in a
two-stage process, first using an event of type
SaveablesLifecycleEvent.PRE_CLOSE followed by an event of type
SaveablesLifecycleEvent.POST_CLOSE. Since firing the
PRE_CLOSE event may trigger prompts to save dirty
saveables, the cancellation status of the event must be checked by the
part after the notification. When removing only non-dirty saveables,
POST_CLOSE notification is sufficient.
The listener is obtained from the part site by calling
The part must not notify from its initialization methods (e.g.
createPartControl), or from its dispose method. Parts that
IReusableEditor must notify when their input is changed
Certain workbench actions, such as Save, target only the active saveables in the active part. For example, the active saveables could be determined based on the current selection in the part.
Copyright (c) 2000, 2017 Eclipse Contributors and others. All rights reserved.Guidelines for using Eclipse APIs.