This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
component:signals [2014/07/10 16:14] vexatos |
component:signals [2014/09/08 20:38] sangar [Screen] |
||
|---|---|---|---|
| Line 39: | Line 39: | ||
| ------ | ------ | ||
| - | - `screen_resize(screenAddress: string, newWidth: number, newHeight: number)` | + | - `screen_resized(screenAddress: string, newWidth: number, newHeight: number)` |
| This signal is queued by [[block:screen|screen]] when their resolution changes, for example because it is manually set via the [[component:gpu|GPU]]. The address is the address of the screen the queued the signal. | This signal is queued by [[block:screen|screen]] when their resolution changes, for example because it is manually set via the [[component:gpu|GPU]]. The address is the address of the screen the queued the signal. | ||
| - `touch(screenAddress: string, x: number, y: number, button: number, playerName: string)` | - `touch(screenAddress: string, x: number, y: number, button: number, playerName: string)` | ||
| Line 79: | Line 79: | ||
| This signal is queued by [[component:redstone|redstone components]] when an incoming signal changes. The address is either that of the [[block:redstone_io|Redstone I/O block]] or that of the computer with the [[item:redstone_card|redstone card]] that generated the signal. The side is one of the [[api:sides|sides]] constants and indicates on which side the signal changed. This is relative to the container of the component, so for computers and robots this depends on which way they are facing. For Redstone I/O blocks this is always the absolute side. | This signal is queued by [[component:redstone|redstone components]] when an incoming signal changes. The address is either that of the [[block:redstone_io|Redstone I/O block]] or that of the computer with the [[item:redstone_card|redstone card]] that generated the signal. The side is one of the [[api:sides|sides]] constants and indicates on which side the signal changed. This is relative to the container of the component, so for computers and robots this depends on which way they are facing. For Redstone I/O blocks this is always the absolute side. | ||
| + | Motion Sensor Block | ||
| + | ------------------- | ||
| + | |||
| + | - `motion(address:string, relativeX:number, relativeY:number, relativeZ:number[, entityName:string])` | ||
| + | Fired by the [[block:motion_sensor|motion sensor]] when a living entity in its line of sight moves faster than the configured sensitivity. | ||
| Network Cards | Network Cards | ||
| Line 113: | Line 118: | ||
| - `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}} | ||