> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/whats-new/2024/march-2024.md).

# March 2024

## Room designer news

Link for demo: <https://roomle.com/t/cp/?configuratorId=mocdemo&id=ps_s06wb5essnwjmd6kh65ikserpvmoql1&api=false&catalogRootTag=rubens_room_demo_root>

### Measurement adaptions

* We implemented snapping logic of measurements line in 2D mode (for object-to-object snapping)
  * It works the same way as snapping while drawing walls but for measurement lines
  * Users can now snap against other objects in the room to measure the distances more precisely

<figure><img src="https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-ec75013383dcffa7e4d807bc88fb2dfb2da9a8f1%2F697e77a4-d75e-42b1-abc7-a79cb4668c43%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

### Camera behaviour adaptions

* New behaviour on adding/switching/duplicating products
  * No camera reset anylonger for those actions
  * Leads to a smoother experience and usage
* Adaptions when it comes to drag and drop of items
  * The catalog drawer is not closed every time you drag an item into the scene

<figure><img src="https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-6eeee5c87641d8436bb28bf843da19ee0ffad51c%2Fd54031cd-eda1-4099-a302-9d4e3aa64521%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

### 2D adaptions in room designer

* 2D arches for (static) construction elements
  * indicating opening direction of the construction element
* 2D displaying of bars for configurable construction elements
  * making selections easier in 2D

Demo example <https://roomle.com/t/cp/?configuratorId=mocdemo&id=ps_s06wb5essnwjmd6kh65ikserpvmoql1&api=false&catalogRootTag=rubens_room_demo_root&constructionRootTag=construction_moc>

<figure><img src="https://2782441740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjLjPj3wCHnfCfuOYQpf4%2Fuploads%2Fgit-blob-4bc30aa90dc871050e9b09f6f84582c2e6b8400f%2F47ec07ff-4e6e-460b-a096-a2c895e9b8f4%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

***


---

# 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://docs.roomle.com/rubens/whats-new/2024/march-2024.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.