Abstract Creates a new ThreeStepEditHandle.
Protected activeIndicates whether the handle is active.
Protected eventedThe EventedSupport used to emit events.
Typically, handles use emitEditShapeEvent to emit "EditShape" events. This is only used in advanced cases, for example when compositing multiple handles.
Called when handle goes from inactive to active state.
The event that triggered the activation
The edit context
Called when the handle leaves the active state.
The event that triggered the deactivation
The edit context
Protected emitEmits an "EditShape" event.
Typically, a handle emits this right after changing the shape.
The shape to emit an edit event for
The status of the edit. Typically, this is IN_PROGRESS while the handle is being dragged / changed, and EditShapeStatus.FINISHED when the drag ends.
Returns the mouse cursor to show.
CreateController will check the active handle's cursor on every map's cursor when the returned cursor string changes.
The default implementation always returns null.
the gesture event to determine a cursor for.
the edit context.
a cursor, or null if no mouse cursor should be shown for this handle.
Populates a context menu with entries.
For example, a handle for a point in a polyline might add a "Delete point" context menu entry.
the input event that triggered opening the context menu.
the edit context
the context menu to add entries to.
a callback that needs to be called when a menu action is performed. Call this at the end of the ContextMenuItem.action implementation.
This method allows the handle to draw shapes on the map.
For example, a point handle draws an icon at its point using EditHandleStyles.handleIconStyle.
A handle can also draw "helper" shapes. These are shapes that are not interactive, but help the user while editing. For example, the base shape of an extruded shape, draped over terrain. Or lines showing how a point can move.
For consistency with built-in handles, it's recommended to draw helper shapes using EditHandleStyles.handleIconStyle.
The default implementation draws nothing.
The GeoCanvas to draw on.
The editing context.
This method allows the handle to draw labels on the map.
For example, you can use this to show coordinates of points, or the current radius of a circle on top of an edit handle.
The default implementation draws nothing.
The label canvas to draw labels on
The editing context.
Handles the given context.
The editing handle can modify the feature (or its shape) based on the type and state of the input event. For example, a drag event that moves a circle.
The default implementation ignores the event.
the gesture event.
the edit context.
Abstract processProcesses an event.
This is typically where you change a shape. For example move a point to where the mouse is dragged, like a PointDragHandle does.
The event to process
The edit context
Abstract shouldWhether the handle should become active.
The event to check
The edit context
Abstract shouldChecks if this handle should deactivate.
The event to check
Abstract shouldThe event to check
Called when (another) handle changes the feature or shape, as indicated by the "EditShape" event.
This handle can update its own state, based on the changed shape.
For example, a PointListInsertHandle just inserted a point in a polyline. The PointListTranslateHandle uses the update to recalculate new sub-handles, based on the new polyline (with the extra point).
The default implementation does nothing.
An event that is emitted whenever this handle changes the shape of a feature.
EditShape
Convenience handle that separates the handling of events in 3 steps:
false).Subclasses should override the methods mentioned above to obtain the desired behavior.
Note that a handle can activate, process and deactivate on a single event. This can be useful, for example to deal with click events (as well as drag events).
One example of a common PointDragHandle, which becomes active when a point is dragged. While dragging, it changes the shape in its
process(). When the drag ends, it deactivates.Since
2022.1