Use of "%" in skin action

Q&A about the latest versions
Post Reply
Howard
Posts: 162
Joined: Wed Jun 03, 2009 5:58 am

Use of "%" in skin action

Post by Howard » Tue Apr 26, 2016 2:17 am

In v. 4 I was able to hide all hotspots by using "%hotspots." This does not seem to work in v. 5; some hotspots hide, others do not. Any ideas what's different?

Thank you.
toggleVis.jpg
toggleVis.jpg (15.82 KiB) Viewed 1640 times
See spiral button on the tool bar here:
http://www.allaroundnevada.com/impossible-railroad/

Howard
Posts: 162
Joined: Wed Jun 03, 2009 5:58 am

Re: Use of "%" in skin action

Post by Howard » Tue Apr 26, 2016 5:12 am

I just discovered that when I change the action to toggle the alpha to 0, rather than toggling the visibility, then using "%hotspots" as the target does indeed affect all instances of hotspots.

Is this workaround necessary? This FORMERLY worked fine with toggling the visibility, in V. 4.

User avatar
Hopki
Gnome
Posts: 9498
Joined: Thu Jan 10, 2008 3:16 pm
Location: Layer de la Haye, Essex UK
Contact:

Re: Use of "%" in skin action

Post by Hopki » Fri Apr 29, 2016 4:07 pm

This is a bug and it has been reported.
Regards,
Hopki

User avatar
Chu
Posts: 89
Joined: Tue Jan 10, 2012 1:59 pm
Location: London, UK
Contact:

Re: Use of "%" in skin action

Post by Chu » Tue May 10, 2016 4:00 pm

Howard wrote:I just discovered that when I change the action to toggle the alpha to 0, rather than toggling the visibility, then using "%hotspots" as the target does indeed affect all instances of hotspots.

Is this workaround necessary? This FORMERLY worked fine with toggling the visibility, in V. 4.
I use "#hotspots.*" which e.g. addresses all beginning with "hotspots" , can you try this and report back?

One drawback using this however, I find is that you cannot connect the same action to other elements with the "|" divides symbol between them as in:

Code: Select all

#hot.*|#hs.*
This DOES NOT address all elements as expected, each has to be expressed as it's own, seperate action, as in:
Mouse Click > ...#hot.*
Mouse Click > ...#hs.*
Using:
Pano2VR PRO 6.1.0 pro 64bit
build 17841/5.12.2

fancybox v3.2.5
Windows 10 v1709
Human Brain v1.0

Image

Artwork
  • Aerosol
  • Design
  • Screen
Specialist
  • 360°
  • Stereoscopy
  • Illusions
Concept
  • Consultancy
  • Campaigns
  • Data
  • Education
est.1971

User avatar
Hopki
Gnome
Posts: 9498
Joined: Thu Jan 10, 2008 3:16 pm
Location: Layer de la Haye, Essex UK
Contact:

Re: Use of "%" in skin action

Post by Hopki » Wed May 11, 2016 12:02 pm

Hi Guys,
In version 5 you would use a skin variable, true/false and the action, Set Variable Value.
This way when you hide the point hotspot, it stays hidden until you select to see it again, regardless if you change nodes with say a drop down menu. The old way using the # or % only hid the point hotspot until you changed nodes then it reappeared again as that was its starting state of the point hotspot.

To set this up is quite easy, but I have broken it down step by step.
Open a two or more node Pano2VR 5 Pro project.
Im saying Pro as this is using pro features but this also works in the standard edition.
Click the skin canvas to get to the skin settings the add the variable.
1.jpg
1.jpg (29.03 KiB) Viewed 1575 times
From the components tool box drag in the Drop-down Silhouette and Node Thumbnail Pro Silhouette components and position them.
I have also added a hide and show button, well its two buttons stacked on top of each other as they are slightly different to show the state of the point hotspot visibility giving the viewer a visual indication if the point hotspot is hidden or showing.
The Drop-down Silhouette menu is positioned top right and anchored top right in its properties panel.
2.jpg
2.jpg (25.98 KiB) Viewed 1575 times
The hotspot template which has the ID ht_node has a logic block set under the alpha.
3.jpg
3.jpg (22.02 KiB) Viewed 1575 times
Im using Alpha as I want the point hotspot to fade in and out and with the Alph logic block I can set a transition and time for the transition.
4.jpg
4.jpg (35.83 KiB) Viewed 1575 times
The logic block condition is when the trigger hs_hide_show is equal to false the the Alpha will be 0.00. The fade will take 1 second as transitions is selected and the time is set to 1 second.

The buttons will set the variable value, so when its true the point hotspot is at alpha 1.00 and when the variable is false, the point hotspot will be at alpha 0.00.

As I'm using variables I will also use this to show and hide the correct buttons, the project opens with the point hotspots visible so I want the Hide Hotspot button to be visible. You would click this to hide the point hotspot and then the show hotspot button would be visible.

So the hide point hotspot button which has the skin ID of hs_hide also has a logic block for its alpha. Its set to alpha 1.00, the logic block looks like this:
5.jpg
5.jpg (39.38 KiB) Viewed 1575 times
It also has the action to set the variable value:
6.jpg
6.jpg (29.16 KiB) Viewed 1575 times
What will happen is as soon as you click this button it will change the variable to false.
When this happens both the point hotspot template and the button will fad out as their logic block conditions state then when the variable is false the alpha for both should be 0.00.

The show point hotspot button starts off at alpha 0.00 and also has a alpha logic block:
7.jpg
7.jpg (38.5 KiB) Viewed 1575 times
When the variable is false the alpha will change to 1.00 so replacing the hide button.
It also has a set variable value action to change the variable back to true.
8.jpg
8.jpg (28.82 KiB) Viewed 1575 times
Using variables means that if you had other point hotspots say for image popups or displaying information you only need to set the logic block in each to hide and show them. This is regardless of skin ID's as its looking at the variable condition.

I have attached two projects, one for Pano2VR 5 Std and the other for Pano2VR 5 Pro so you can see it working.
The project opens with the point hotspot and the hide point hotspot button showing.
Click the hide point hotspot button it will fade into the show point hotspot button with the point hotspot fading out.

Using the drop down menu you can change nodes to Image Two and the point hotspot is still hidden. Only when you click the show point hotspot button will it appear.

Of course this is not just for point hotspot templates, you can use this to hide and show anything.
Example, taking the attached project you could open the skin and select the container Dropdown Menu.
Set its alpha to 0.00 then under its alpha logic block add the condition:
9.jpg
9.jpg (40.6 KiB) Viewed 1575 times
What will happen is the drop down menu will be hidden when the point hotspots are showing.
Hide the point hotspots and the drop down menu will then show. This then gives the viewer the option to navigate using either the point hotspots or drop down menu.

Have fun,
Hopki
Attachments
hotspot_hide_show_pro.zip
(618.11 KiB) Downloaded 55 times
hotspot_hide_show_std.zip
(566.32 KiB) Downloaded 49 times

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 8 guests