forked from node-red/node-red
-
Notifications
You must be signed in to change notification settings - Fork 0
Design: Editor Events
Nick O'Leary edited this page Jul 10, 2015
·
6 revisions
The follow components emit events for the internal workings of the editor. Need to decide if it makes sense to expose these directly as part of the API, or hide them behind a single RED.events component.
| Component | Event | Args | Description |
|---|---|---|---|
RED.nodes |
change |
{ dirty: true/false } |
The 'dirty' state of the flow has changed. |
RED.sidebar |
resize |
The sidebar has changed size. | |
RED.view |
selection-changed |
{ nodes: [], link: link } |
The node selection has changed. |
RED.workspaces |
change |
{ old: 'tab-id', workspace: 'tab-id' } |
The visible workspace tab has changed |
| Event | Args | Description |
|---|---|---|
nodes:change |
{ dirty: true/false } |
The 'dirty' state of the flow has changed |
sidebar:resize |
The sidebar has changed size | |
view:selection-changed |
{ nodes: [], link: link } |
The node selection has changed |
workspace:change |
{ old: 'tab-id', workspace: 'tab-id' } |
The visible workspace tab has changed |
deploy |
A flows have been deployed successfully |