This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
component:signals [2014/07/10 12:13] sangar created |
component:signals [2014/07/10 16:15] vexatos |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Signals | ||
+ | ====== | ||
Signals are messages sent to a computer from some external source and can be used for many purposes. They always have at least a name, and may have any number of (simple) parameters. Note that computers may also queue signals on themselves. | Signals are messages sent to a computer from some external source and can be used for many purposes. They always have at least a name, and may have any number of (simple) parameters. Note that computers may also queue signals on themselves. | ||
Line 111: | Line 113: | ||
- `carriage_moved(success: boolean[, reason:string[, x:number, y: number, z: number]])` | - `carriage_moved(success: boolean[, reason:string[, x:number, y: number, z: number]])` | ||
This signal is queued by the carriage component after a move or simulate command was issued. The `success` parameter indicates whether the move or simulation was successful, i.e. whether the carriage could be moved. If the move failed, `reason` is the error message. Depending on the error message, (`x`, `y`, `z`) is the world coordinate of the block that caused the move to fail. | This signal is queued by the carriage component after a move or simulate command was issued. The `success` parameter indicates whether the move or simulation was successful, i.e. whether the carriage could be moved. If the move failed, `reason` is the error message. Depending on the error message, (`x`, `y`, `z`) is the world coordinate of the block that caused the move to fail. | ||
+ | |||
+ | Contents | ||
+ | ----------- | ||
+ | {{page>api:contents&noheader&noeditbutton&nouser&nofooter}} |