Michal Rykiert

Problem fixed in the newest 2024 build and in 2025.

Done and available in 2025 R2 :)

Done and available in 2025 R2 :)

It is indeed quite specific scenario. The behavior you experienced is what we expect to happen and we plan to keep it as is for the forseeable future.

Most likely we'll address it by making this suggestion a reality: https://community.webcon.com/forum/thread/7105?page=1#m7161 :). I'm closing the thread, but please stay tuned for updates on the thread linked above :)

Good idea, we're going to review it and decide on how to proceed further.

I agree that it could be a nice touch, although given many other things in the backlog with higher priority, realistically, we won't have the capacity to add it to our development schedule.

Good idea. We're putting it straight to the backlog :)

We understand the use case, however introduction of such functionality product-wide poses some security challenges with the Portal in a web browser. After a consideration of other that and other priorities, for now we're not going to proceed with the implementation.

Hi Sebastian, we're already working on a new, web-based Studio which will have an improved navigation. So expect improvements there. At the same time, since the web-based Studio project is ongoing, we're not going to provide improvements to the current Studio.

We'll analyze the possibilities of the integration. Stay tuned.

Agreed. Your suggestion goes straight to the backlog :).

It's already on our radar and we're planning on expanding Designer Desk's capabilities. I'm changing the status to Under Review.

Sebastien, we'll consider your suggestion during the work on the new Designer Studio (already ongoing). Otherwise, since the case has been cleared out, I'm closing the thread.

It makes sense >> straight to the backlog.

Sounds good, we'll put it under review.

Sounds good -> straight to the backlog.

Working on it! >> backlog

Since the comment section is a default option, available everywhere, we want to keep it relatively simple. Therefore, as such, the comment section will not be developed in this direction. However, we will consider adding a new field type that would allow for the behavior as you suggested. With

We'll put it under consideration :). I'm changing the status accordingly.