Difference between revisions of "Layerservice"
|Line 234:||Line 234:|
Revision as of 10:58, 5 February 2014
- 1 Layerservice
- 1.1 Special Selectors
- 1.2 layers
- 1.3 kids
- 1.4 parts
- 1.5 models
- 1.6 materials
- 1.7 textures
- 1.8 clips
- 1.9 vmaps
- 1.10 verts
- 1.11 polys
- 1.12 edges
- 1.13 uvs
- 1.14 polsets
- 1.15 vrtsets
- 1.16 itmsets
- 1.17 selection
- 1.18 selmode
Commands are executed and queried directly through the command syntax description previously in this guide, but this doesn’t provide any detailed information about meshes and their related elements.
The layerservice ScriptQuery can be used to obtain this detailed mesh information.
Many item-level operations in layerservice have been superseded by those in Sceneservice. Be sure to check Sceneservice to see if it is more appropriate to your task than layerservice. In general, when you want to deal with items and their channels or when you want scene-level information, you'll mostly be making use of sceneservice. When you want to deal with modeling operations or need to obtain information about the specific vertices, polygons and edges of a mesh, you'd use layerservice.
Due to its design, layerservice is only meant to work on mesh items. Attempting to pass other kinds of items to any of the attributes will fail.
This interface hosts a series of global lists of layers, models, materials, parts, textures, clips and vertex maps. There are also local lists specific to the layer selection for accessing vertices, edges and polygons.
The root-level attributes ending in an ‘s’ all return valid selectors for the more specific property attributes, similar to how the return values from the Commandservice commands and Categories attributes are the selectors for the more specific property attributes. However, the layerservice ‘s’ attributes require the use of selectors returned by the various attributes ending in _groups to filter the query to specific groups of elements.
The ‘s’ attributes are layers, kids, materials, parts, textures, clips, vmaps, verts, polys, edges and models.
The _groups attributes are layer_groups, kid_groups, material_groups, part_groups, texture_groups, clip_groups, vmap_groups, vert_groups, poly_groups and edge_groups.
In the case of layers, the _groups attribute returns the keywords main, fg, bg and all. Getting a list of foreground layers is done in the following example.
query layerservice layers ? fg
Each of the values returned by this query can be passed into the a more specific property attribute, such as layer.subdivLevel. In the following example we assume that the query returned "0", and we provided that as the selector to layer.subdivLevel:
query layerservice layers.subdivLevel ? 0
Alternatively, all of the different ‘s’ attributes support the list walking keywords returned by the layers_element attributes first, last, next and prev, which are fairly self-explanatory. This example returns the first vertex map:
query layerservice vmaps ? first
The result of this query can then be passed to the property attributes. The next vertex map can then be obtained with:
query layerservice vmaps ? next
And so on.
In the case of vertices, edges and polygons, a layer selection is required before any of their attributes can be used. This can be done by using any of the layer attributes that takes a selection.
The layer.index attribute, for example, actually gets the index of a specific layer, but it also changes the selection in the service.
In this example we switch the layer selection to the primary layer, discarding the returned value:
query layerservice layer.index ? main
After that, the various vertex, polygon and edge attributes can be used to get information specifically related to that layer, such as this query to get the number of selected vertices in the layer:
query layerservice vert.N ? selected
The above example also demonstrates the different grouping keywords used by the local lists. A complete list of keywords can be obtained by querying vert_groups, edge_groups and poly_groups, and includes selected, unselected, and all.
"Selecting" Layers, Vertex Maps, etc.
As mentioned above, it is important to note that all attributes work only on the current layer chosen for querying. This is especially true of the vert.???, poly.??? and edge.??? element attributes.
This is termed as selection, but is not the same as how you select elements with the mouse through the interface; rather this is to provide layerservice with a context to query another attribute. This kind of selection is performed by simply querying one of the attributes of the element you want to select.
For example, to "select" a layer, simply query any layer.??? attribute, such as layer.index.
query layerservice layer.index ? main
After this, the various vert.???, poly.???, etc. attributes can be used. The return value from the query above can be ignored; our only purpose is to tell layerservice which layer we plan to query the properties of.
Once "selected", it remains until a new call to one of the layer.??? attributes.
Similarly, attributes such as vert.vmapValue and poly.vmapValue require a vertex map selection, as mentioned in the attribute’s description
Selecting Points, Polygons and Edges
The select.element command can be used to select vertices, polygons and edges (this is selecting like how you would select a polygon in a model viewport, not the query selecting described in the previous section).
Once selected, elements can be manipulated using other commands. In all cases, the selectors returned by the verts, polys and edges attributes can be used to select those individual elements. verts and polys bother return element indices, while edges returns a vertex pair separated by commas and wrapped in parentheses, such as "(21, 18)".
The model series of attributes provide information about the models, which are defined as a collection of layers stored in a file.
The model attribute itself will return the list of available model.??? attributes.
The model.??? attributes query specific properties of an individual model. For each, the selector must be a specific selection from a models query, or an index between 0 and model.N, or one of the models_groups selectors.
Get a list of model attributes. No selection is needed.
query layerservice model ?
[list of model.??? attribute names]
Get the number of models in memory.
query layerservice model.n ?
Get the filename of the model, or an empty list if it has not yet been saved. This is the filename only, without the path to the file.
query layerservice model.name ? 0
Index of a model in the global model list. Note that the indices start from 1.
query layerservice model.index ? 0
Return the index of the current layer of the model. Layer indices start from 1.
query layerservice model.layer ? first
Get the name of the current model. If the file has not yet been saved, this may be "untitled" or "untitled*".
query layerservice model.curName ?
Return the currently selected model’s index. Indices start from 1.
query layerservice model.curIndex ?
Get the filename of the model, or an empty list if it has not yet been saved. This includes the full path to the file as well as the filename.
query layerservice model.file ? 0
The material attribute is use to get the list of available material.??? attributes. used to provide group filters for the other attributes.
The materials attribute returns a list of possible, specific selectors for the various material.??? attributes, while material.N returns the number of materials in that grouping. Both attributes require a keyword from the material_group attribute as a selector.
Get a list of material attributes. No selection is needed.
Example: query layerservice material ?
Result: [list the material.??? attribute names]
Description: Get a list of group keywords for use as the selection for the other attributes. No selection is needed.
Example: query layerservice material_groups ?
===materials=== depricated? Get a list of selectors for the material.??? attributes. These are in the form of absolute indices into the global materials list. Material indices start from 0.
Example: query layerservice materials ?
Get the number of materials.
Example: query layerservice material.n ? all