public interface ILinkedModeListener
LinkedModeModel
s to communicate state changes, such
as leaving linked mode, suspending it due to a child mode coming up, and
resuming after a child mode has left.
This interface may implemented by clients.
Modifier and Type | Field and Description |
---|---|
static int |
EXIT_ALL
Flag to
leave specifying that all nested modes should
exit. |
static int |
EXTERNAL_MODIFICATION
Flag to
leave specifying that document content outside of
a linked position was modified. |
static int |
NONE
Flag to
leave specifying no special action. |
static int |
SELECT
Flag to
leave specifying that a UI of a parent mode should
select the current position. |
static int |
UPDATE_CARET
Flag to
leave specifying that the caret should be moved to
the exit position. |
Modifier and Type | Method and Description |
---|---|
void |
left(LinkedModeModel model,
int flags)
The leave event occurs when linked is left.
|
void |
resume(LinkedModeModel model,
int flags)
The resume event occurs when a nested linked mode exits.
|
void |
suspend(LinkedModeModel model)
The suspend event occurs when a nested linked mode is installed within
model . |
static final int NONE
leave
specifying no special action.static final int EXIT_ALL
leave
specifying that all nested modes should
exit.static final int UPDATE_CARET
leave
specifying that the caret should be moved to
the exit position.static final int SELECT
leave
specifying that a UI of a parent mode should
select the current position.static final int EXTERNAL_MODIFICATION
leave
specifying that document content outside of
a linked position was modified.void left(LinkedModeModel model, int flags)
model
- the model being leftflags
- the reason and commands for leaving linked modevoid suspend(LinkedModeModel model)
model
.model
- the model being suspended due to a nested model being
installedvoid resume(LinkedModeModel model, int flags)
model
- the linked mode model being resumed due to a nested mode
exitingflags
- the commands to execute when resuming after suspend
Copyright (c) 2000, 2014 Eclipse Contributors and others. All rights reserved.Guidelines for using Eclipse APIs.