Get desktop application:
View/edit binary Protocol Buffers messages
* This is a path to an element within a library from the root of a library. To be used as a way to reference such elements.
Used in: , , , , , , , , , , , , , ,
* This is a path from a local context to some other local context. To be used as a reference.
Used in: , , , , , , , , , , , ,
* This is an actual step you take within the local environment. The directions encode the type of thing we are referencing, but to the user all of these look just like local variables
Used in: ,
Allocates a new element in an array, valid for arrays only. Empty string means automatically allocated, while a non-empty string is a suggested name.
* A local name is what something is called in the context of its parent, whether that parent is a namespace (as in the library) or some other element (as in a design or heirarchy block). localNames should have the following properties: - First char is a lower case letter - All other chars must be letters, numbers, '-', '<', '>' - lowerCamelCase is preffered, don't use any symbols in the name if possible. These are style guidelines, literally any string will work.
* These are reserved terms that we'll end up using in various places. I'd rather have these in the block/link/bridges where they're going to exist, but that's not possible without polymorphism protibuf doesn't have
Used in:
* Directions we could move
* reserved parameters
true implies CONNECTED_LINK resolves; not available on PortArray
EXISTS = 41;
available on PortArray and LinkArray
available on PortArray and LinkArray, returns a list of string of element names
cannot be used as a generator dependency
available on PortArray, returns a list of string of incoming connection names,