Garden Gnome Software

Good morning all,
I have the following problem and can not find the solution.
I wrapped a skin with a Maker (arrow) always shows the active panorama in the menu on the page. So I click on Panorama 1 and my arrow moves to the menu item Panorama 1. If you click on Panoarama 2 in the menu, the arrow moves to menu item 2. If a panorama is called up via a hotspot, the arrow also moves to the desired menu item. Thus, the viewer always has an overview of where he is.

I used this skin for several objects for a client and just modifiez the links, texts and menu items in the skin. Unfortunately, this works no longer with the Maker (arrow) The arrow moves to the menu item when I call the panorama on the menu bar, but not when I call the panorama via a hotspot.

Here is a link to the working skin and a picture of the action in the skin.

http://kunden.patrickjelen.de/web/index.html

Hi,
I take it you found the problem as when testing your link I get the arrow moving when using either the hotspot or menu.
Regards,
Hopki

Hi Hopki,
No, unfortunately not. If I use this skin (link) for another job this will not work. The arrow only moves to the desired object when I click directly on the item in the menu. But not about the hotspot. Then the arrow (marker) simply stops.

Should I send you the skin?

Thanks
Patrick

Hi Patrick,
Yes please.
Regards,
Hopki

Hi Patrick,
Looking at your skin and the menu I would have used node markers.
The reason why is a node marker can detect that the node is active.
So it does not matter how you get to a node it can still react.

In your skin rather than remake it you can just add node markers for each menu item.
Example:
Add node marker and position X:0 Y:0
Give the ID: Link1 Marker
Under the node markers properties and the Node Marker tab add Node: DJH Essen
Give it the action: Activate, Trigger Click, Link_1

Make for for each menu item making sure it Node is linked to the correct node.
As that node becomes active it creates a trigger click that then moves the pointer to the correct position.

Moving forward you would use node markers with the text box as the child element.
Regards,
Hopki

Thank you Hopki!
I have found the main error. It was the Hotspotproxy ID that was wrongly registered.

Now it works perfect again..........