Tag filter not applied to Dropdown Cloner in two level dropdown menu

Q&A about the latest versions
Post Reply
User avatar
dennisvanduijn
Posts: 145
Joined: Wed Apr 28, 2010 10:56 am
Location: Gouda, Netherlands
Contact:

My problem is quite hard to explain. First, let's show my working example:

http://okijk.nl/test/pano2vr/01

I use the 'Drop-down Silhouette' in the 'Components Toolbox' as a basis. Left menu is the topmenu, right is the submenu. I like to have the topmenu function as a filter, so that 'SPT' only shows 'SPT 01' and 'SPT 02' in the submenu, etc. So, if 'Dropdown Menu Text' is clicked, I set the value of the submenu 'Dropdown Cloner' to '$ut'. That doesn't work. The submenu is not filtered, all panos are listed. If I add the same action to the white textboxes at the right, it works! The submenu only shows the items belonging to the specific filter, like it should.

It drives me mad. Why is the exact same action working in a hard coded button and not when it is added to the cloner?

Any thoughts?
Commercial 360° tours ● Gamified 360° tours ● Officially since 2010

Image

https://okijk.nl
User avatar
Hopki
Gnome
Posts: 13028
Joined: Thu Jan 10, 2008 3:16 pm
Location: Layer de la Haye, Essex UK
Contact:

Hi Dennis,
I just removed my last post as I just found an easy fix.
All you have to do is add # in front of the target.
This is because a cloned element is not in the same level as all the other skin elements. The # makes it look further and also in cloners.

So as an example:
Mouse Click, Set Value, $us, #Dropdown Cloner_2
Iv just tried it and all working.
Regards,
Hopki
Garden Gnome Support
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
User avatar
dennisvanduijn
Posts: 145
Joined: Wed Apr 28, 2010 10:56 am
Location: Gouda, Netherlands
Contact:

Hi Hopki,
Thank you for your efforts, it works!

To me it smells like a change request :wink:. In the Actions Settings pop-up, the Target pulldown menu is already smart enough to find the right Target while typing. Why not throw an exclamation mark when the Target hasn't been found while typing and then offer a checkbox which can add the '#' in the background? Like: 'target not found, enable smart search?' Just an idea.

But thanks again, you really helped me!

Dennis
Commercial 360° tours ● Gamified 360° tours ● Officially since 2010

Image

https://okijk.nl
User avatar
Hopki
Gnome
Posts: 13028
Joined: Thu Jan 10, 2008 3:16 pm
Location: Layer de la Haye, Essex UK
Contact:

Hi Dennis,
I guess this would introduce bugs as what if what your looking for not acutely in the skin, you than add a # and then it still does not work.
Pano2VR has always required a # in front of things like hotspot template targets as the action to hide a template will only hide one, add the # and it then digs deeper and finds and hides them all.

This has been the way since version 3.x. In version 3.x the skin actually had text saying this but this was dropped in version 4.
Having a prompt for elements that need this such as hotspot templates, node markers and cloners is a good idea and I will raise a feature request, may be a popup tool tip, lets see what the devs say.
Regards,
Hopki
Garden Gnome Support
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
User avatar
dennisvanduijn
Posts: 145
Joined: Wed Apr 28, 2010 10:56 am
Location: Gouda, Netherlands
Contact:

Clear explanation and nice to know that it might be picked up!
Commercial 360° tours ● Gamified 360° tours ● Officially since 2010

Image

https://okijk.nl
Post Reply