| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
| |
Needs a tidy-up
|
| |
|
|
|
|
| |
Always sets the target unit before binding, allows specifying the unit
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Returns a collection of links/nodes without adding them to the network, suitable for displaying in the UI
during a design/build process
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
something
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This was a pain... but all the coords make much more sense now and a lot of mystery negation has disappeared.
|
| |
|
|
|
|
| |
Encompasses determining a route and a distance to travel
|
| |
|
| |
|
|
|
|
|
| |
This makes more sense when you realise that the existing navigation
workings work on exactly the same type!
|