I'll try to explain a little more fully.
I am engaged in creating virtual tours for real estate objects. At the moment, the task that I would like to solve is to increase the functionality of the virtual tour - adding the ability to choose a real estate object directly on the panorama. Since the information about the status of units and their price is constantly changing, the only possible option to keep the data up-to-date is to configure its automatic updating. And this can be configured using the API. Each unit in the virtual tour is represented as a node. When automatically updating from the database, the values are set to the custom fields of the corresponding node.
- 2023-07-13_17-46-19.png (21.9 KiB) Viewed 4295 times
I need each unit on the panorama to be marked with a polygon and have its own label. Depending on the status (available or not for sale) this label or polygon is active or inactive. Here is a short example of how I would like it to look like:
https://aerostudio360.ru/vt/testpoly2/
Here, when you hover over the unit label or on the polygon of this unit, the label changes its appearance. The left placemark and polygon are active - a unit opens by clicking. The right placemark and polygon are inactive - information appears on hover, but the transition does not occur.
Due to the fact that the polygon "does not see" the values of the user fields of the node attached to it (I showed this in the previous post), then we also have to make polygons unique, assign a unit number to each polygon and assign a value when updating: is the unit available or not.
The second problem is that since polygons have become unique, you have to create your own proxy double for each polygon in the skin editor in order to assign a hover or click action. And there can be more than one hundred units in one project.
I do not know how feasible it is in principle to add a Skin-ID for polygons, but it seems to me that this would greatly simplify the possibilities of using polygons in virtual tours.