Replies: 1 comment
-
Given your description you should absolutely stick to markers. As the documentation says overlays are for big elements, covering the whole panorama (or a good part of it), this was originally a core feature (and still is a version 5.4). You cannot achieve the "x-ray" effect of the overlays demo with a marker, the plugin allowing smaller overlays is just a bonus. It was also implemented as a personal (non working) prototype to reimplement Myst 3 game which features cubemap scenes with embedded videos. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on a project where we display markers on top of a panorama that the user can interact with (mainly hover and display a tooltip, edit or delete them in-situ) and there are some other, completely different, markers whose sole purpose is to click on them and load a different panorama. Since the introduction of Overlays plugin I have been tasked with replacing the latter markers with overlays. This is due to these markers being only clickable, same as overlays (as seen on the documentation), and because we want to separate concerns and responsibilities:
So, my question here is: What is the main purpose of overlays, and how do these differ from Markers? If there were a Venn diagram with Markers and Overlays use cases on each side, would there be a use-case intersection of both?
I've already read all the documentation and sense that we should stick with Markers on both scenarios, but I'm not convinced yet. Also, just to point this out, these markers are generated programmatically and there would be more than one on the panorama image at the same time.
Beta Was this translation helpful? Give feedback.
All reactions