Hi, New to skins. I appreciate any advice or links to resources.
I've used the Orb Map Popup component in my skin (basically the skin just has the map, full screen and minimize icons). I haven't changed any settings of the map component, other than to specify which floor plan to use.
I'm having an issue where if the viewer doesn't render correctly AND it doesn't show the whole map block with description if the window is 1024 pixels wide or less. It has an artifact that looks like it's added a bunch of map pins to a smaller window overlapping the map. It works well when the width of the window is 1025 or wider (width='1025') or in fullscreen. It also doesn't show the description or title in the smaller size.
Any ideas?
1025 pixels wide
1024 pixels wide, red circle highlights the problem area of pins
Orb Map Popup error in non-full screen view
Hi,
Do you have a link to the project?
I just tried to replicate the issue but it's all working as expected.
It looks like you have an additional layer somewhere. Can you upload the skin .ggsk file.
Tony
Do you have a link to the project?
I just tried to replicate the issue but it's all working as expected.
It looks like you have an additional layer somewhere. Can you upload the skin .ggsk file.
Tony
Tony Redhead | Panoramic Photographer | mobile: +61438501002 | website: https://tonyredhead.com - https://redsquare.com | Pano2VR Tutorials: https://tonyredhead.com/pano2vr | instagram: https://www.instagram.com/tonyredhead/
-
- Posts: 11
- Joined: Tue Jul 11, 2023 12:29 pm
Thanks for the Reply Tony,
I'll try to post the skin file later tonight.
I'll try to post the skin file later tonight.
-
- Posts: 11
- Joined: Tue Jul 11, 2023 12:29 pm
Hi Tony,
Please see the attached skin file. And, thanks for taking the time to help me out.
H
Please see the attached skin file. And, thanks for taking the time to help me out.
H
Hi,
Seeing the skin makes it much easier to see what's going on.
1. You seem to have modified the skin in a number of different ways. I can see you have moved the element "map_phone" from the element "screentint_phone" to the top root of the tree.
2. This element, now exposed, has an Alpha logic block with a variable "resp_phone" trigger that hides the map when its false.
3. The variable "resp_phone" in turn has a logic block that sets the variable to true when the screen size is less than 1024px. Thus displaying the phone version of the map.
To test just cut the element "map_phone" and output. The additional map goes away. I'd go back to the original skin version of the "screentint_phone" element.
Tony
Seeing the skin makes it much easier to see what's going on.
1. You seem to have modified the skin in a number of different ways. I can see you have moved the element "map_phone" from the element "screentint_phone" to the top root of the tree.
2. This element, now exposed, has an Alpha logic block with a variable "resp_phone" trigger that hides the map when its false.
3. The variable "resp_phone" in turn has a logic block that sets the variable to true when the screen size is less than 1024px. Thus displaying the phone version of the map.
To test just cut the element "map_phone" and output. The additional map goes away. I'd go back to the original skin version of the "screentint_phone" element.
Tony
Tony Redhead | Panoramic Photographer | mobile: +61438501002 | website: https://tonyredhead.com - https://redsquare.com | Pano2VR Tutorials: https://tonyredhead.com/pano2vr | instagram: https://www.instagram.com/tonyredhead/
-
- Posts: 11
- Joined: Tue Jul 11, 2023 12:29 pm
Hi Tony,
First of all, thank you so much for your detailed explanation. I'm learning a lot.
I forgot I had added the Feather Orb Hotspots component as well. That seems to add the screentint_phone element. The map_phone element is part of the Orb Map Popup component and is NOT part of the Feather Orb Hotspot which is why it looks like it was moved.
However, even removing the Feather Orb Hotspots component and only using the Orb Map Popup Component, I still get the undesired behavior, because, as you said, the logic block is still there. Until, as you recommend, I remove the map_phone element which removes the overlay issue. This brings up some other sizing and display issues that I will dig into for a bit before I take more of your time. This is just an FYI for any future readers that may run into a similar issue.
This software is incredibly complex and customizable and I look forward to learning more about it. Your generous response is very helpful in sending me along the right tracks.
Thanks again.
Henry
First of all, thank you so much for your detailed explanation. I'm learning a lot.
I forgot I had added the Feather Orb Hotspots component as well. That seems to add the screentint_phone element. The map_phone element is part of the Orb Map Popup component and is NOT part of the Feather Orb Hotspot which is why it looks like it was moved.
However, even removing the Feather Orb Hotspots component and only using the Orb Map Popup Component, I still get the undesired behavior, because, as you said, the logic block is still there. Until, as you recommend, I remove the map_phone element which removes the overlay issue. This brings up some other sizing and display issues that I will dig into for a bit before I take more of your time. This is just an FYI for any future readers that may run into a similar issue.
This software is incredibly complex and customizable and I look forward to learning more about it. Your generous response is very helpful in sending me along the right tracks.
Thanks again.
Henry