> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2019/2019.4.3.0-november-21-2019.md).

# 2019.4.3.0 - November 21, 2019

### Catalog

* Number attribute is here! Now Products can pass number data to 3D assets to configure things like size and positioning.
* Take even more advantage of smart assets using one asset for multiple Catalog items. For example:
  * Create one material asset with a “color” attribute: “Colored Leather”
  * Create three Catalog items: “Blue leather”, “Green leather”, “Red leather”
  * Reference the “Colored Leather” asset for each Catalog item to expose the configuration field
  * Set the color per item like: {“color”:”#FF0000”}. Repeat for each item.

### Editor

* Auto-save is here! Threekit saves as you work so you don’t have to remember to click the Save button
* Drag and drop models from the Asset panel directly into your scene tree
* Local, World, and View modes have been added to manipulators to give you more control: select a manipulator like Move or Rotate to expose the menu.
* The editor camera now has auto near/far clipping

### 3D

* Annotation support has been added to the Scene graph
* Threekit now supports Triplanar mapping
* Min/Max Zoom and Min/Max Azimuth angle support is here
* Canvas operators now support opacity


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community.threekit.com/releases/2019/2019.4.3.0-november-21-2019.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
