> 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.7.0-december-18-2019.md).

# 2019.4.7.0 - December 18, 2019

#### Catalog

* Server-side pagination has been added to the Catalog Items listing so that we can load hundreds of thousands of items without slowing you down
  * Pagination controls have been updated as well you can set how many items you see in your listing.
* Now you can disable AR and Sharing when you embed the Threekit player
  * Use the boolean parameters `showAR` and `showShare`

#### Assets

* Server-side pagination has been added to the Asset listing so that we can load hundreds of thousands of items without slowing you down
  * Pagination controls have been updated as well you can set how many items you see in your listing.
* Now you can view Materials in the Threekit Player with Threekit’s Material View
* Importing has been revised so that assets are created only when needed

#### Editor

* Server-side pagination has been added to the Assets panel as well. Threekit dynamically fetches assets as you scroll.
* Basic Annotation support has been added
  * Right-click anywhere in your scene tree and add an Annotation. Position it in 3D space and give it some custom text
* Like autosave but want to turn it off for a bit? Now you can toggle autosave and save when you want
* Now when you’re editing Materials, you’ll see them apply to Threekit’s Material View


---

# 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.7.0-december-18-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.
