This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
api:component [2015/01/14 23:40] 127.0.0.1 external edit |
api:component [2018/06/15 21:47] ldentityunknown component.list() |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| Calls the method with the specified name on the component with the specified address, passing the remaining arguments as arguments to that method. Returns the result of the method call, i.e. the values returned by the method. Depending on the called method's implementation this may throw. | Calls the method with the specified name on the component with the specified address, passing the remaining arguments as arguments to that method. Returns the result of the method call, i.e. the values returned by the method. Depending on the called method's implementation this may throw. | ||
| - `component.list([filter:string[, exact:boolean]]):function` | - `component.list([filter:string[, exact:boolean]]):function` | ||
| - | Returns an iterator over all components currently attached to the computer, providing tuples of address and component type. Use it like so: `for address, componentType in component.list() do ... end` | + | Returns a table with all components currently attached to the computer, with address as a key and component type as a value. It also provides iterator syntax via `__call`, so you can use it like so: `for address, componentType in component.list() do ... end` |
| If `filter` is set this will only return components that contain the filter string (this is *not* a pattern/regular expression). For example, `component.list("red")` will return `redstone` components. | If `filter` is set this will only return components that contain the filter string (this is *not* a pattern/regular expression). For example, `component.list("red")` will return `redstone` components. | ||
| If `true` is passed as a second parameter, exact matching is enforced, e.g. `red` will *not* match `redstone`. | If `true` is passed as a second parameter, exact matching is enforced, e.g. `red` will *not* match `redstone`. | ||
| Line 27: | Line 27: | ||
| - `component.setPrimary(componentType: string, address: string)` | - `component.setPrimary(componentType: string, address: string)` | ||
| Sets a new primary component for the specified component type. The address may be abbreviated, but must be valid if it is not `nil`. Triggers the `component_unavailable` and `component_available` signals if set to `nil` or a new value, respectively. | Sets a new primary component for the specified component type. The address may be abbreviated, but must be valid if it is not `nil`. Triggers the `component_unavailable` and `component_available` signals if set to `nil` or a new value, respectively. | ||
| - | - `component.list([filter: string]): function` | + | |
| - | Returns an iterator which returns pairs of `address, type` for each component connected to the computer. It optionally takes a filter - if specified this will only return those components for which the filter is a substring of the component type. For example: | + | Note that the component API has a metatable that allows the following syntax: |
| - | ```lua | + | |
| - | local component = require("component") | + | |
| - | -- prints `redstone` for each attached redstone card. | + | |
| - | for _, name in component.list("red") do print(name) end | + | |
| - | ``` | + | |
| - | Note that the component API has a metatable that allows the following syntax: | ||
| ```lua | ```lua | ||
| local component = require("component") | local component = require("component") | ||
| Line 42: | Line 36: | ||
| print(rs0 == rs1) -- true | print(rs0 == rs1) -- true | ||
| ``` | ``` | ||
| + | |||
| + | |||
| Contents | Contents | ||
| ----------- | ----------- | ||
| {{page>api:contents&noheader&noeditbutton&nouser&nofooter}} | {{page>api:contents&noheader&noeditbutton&nouser&nofooter}} | ||