Built a tour with v.6.1.8 Pro using simplex_v6.ggsk. Now I would like to add a splash image but when I open the skin editor the top node of the tree is called "do_not_modify_skin" and the canvas shows a warning to only use the skin configuration tool. Does that mean I can't add my splash screen?
It would be good to have some discussion of the "do_not_modify_skin" node in the docs.
"do_not_modify_skin" -- what does it mean?
It's my understanding the V6 skin (simplex and silhouette) was designed and built to provide a very comprehensive skin that included maximum flexibility without editing. The flexibility comes from the design and scope of the Variables which can be modified via the Skin Configuration button in the Output panel. Here you can change Skin Colors and define which Skin Parameters you want to use.
In order to achieve this flexibility, there are a lot of interconnected logic blocks for the elements, and editing these connections can be very tricky and it's very easy to break the skin if you are not careful. So for the inexperienced skin builder, the "do_not_modify" warning can be compared to a warning sign like "Slippery when Wet".
This is not to say you can't modify the skin but you must proceed with caution and you are responsible for any issues that may occur as part of your actions.
cheers,
Tony
In order to achieve this flexibility, there are a lot of interconnected logic blocks for the elements, and editing these connections can be very tricky and it's very easy to break the skin if you are not careful. So for the inexperienced skin builder, the "do_not_modify" warning can be compared to a warning sign like "Slippery when Wet".
This is not to say you can't modify the skin but you must proceed with caution and you are responsible for any issues that may occur as part of your actions.
cheers,
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/
-
tksharpless
- Posts: 89
- Joined: Wed Aug 27, 2008 11:24 pm
Right, I get that. But some essential parameters now seem to be inaccessible - or should I say even more inaccessible than before. Case in point: how the hell do I change the default autorotation speed?
Hi,
cheers,
Tony
That is set in the Project > Output > Auto Rotation & Animation panel.Case in point: how the hell do I change the default autorotation speed?
- AutoRotation.jpg (84.24 KiB) Viewed 1615 times
cheers,
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/
Yes, that confused me too. 
I could see the tt_autorotate flag was being set in the javascript but the default speed was too fast when using the autorotate button in the Simplex template.
I also has a longish timer in there that I couldn't turn off.
Setting it up as Tony shows, but making it inactive overrides that 'built in' value and stopped it kicking in automatically too.
I then decided I might as well have it activated as well, but only after 30 seconds, so it doesn't kick in too soon and annoy people.
I'm guessing the code needed some default values to prevent errors; but they aren't exposed, only overridden with the appropriate flags/values.
When setup as above it adds this line to the pano.xml file:
<autorotate enabled="1" useanimation="0" speed="0.100" startloaded="1" delay="30.00" returntohorizon="0.000"/>
It gets confused and starts rotating when you switch from Portrait to Landscape mode, but you'd probably only do that once.
I could see the tt_autorotate flag was being set in the javascript but the default speed was too fast when using the autorotate button in the Simplex template.
I also has a longish timer in there that I couldn't turn off.
Setting it up as Tony shows, but making it inactive overrides that 'built in' value and stopped it kicking in automatically too.
I then decided I might as well have it activated as well, but only after 30 seconds, so it doesn't kick in too soon and annoy people.
I'm guessing the code needed some default values to prevent errors; but they aren't exposed, only overridden with the appropriate flags/values.
When setup as above it adds this line to the pano.xml file:
<autorotate enabled="1" useanimation="0" speed="0.100" startloaded="1" delay="30.00" returntohorizon="0.000"/>
It gets confused and starts rotating when you switch from Portrait to Landscape mode, but you'd probably only do that once.