Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Thanks Klaus,Hi,
for anyone having the Windows issue - there is a new release (build 2023-02-09) available that should fix it.
Actually the problem was the same as in 1.20.10 and related to the NWJS version:
krpano 1.20.10
At that time I had changed the NWJS version in 1.20.10, but unfortunately somehow forgot to apply that change also to 1.21...
Best regards,
Klaus
Now it opens everything perfectly, the testing-tour works only if I build a tour, if you run it from the main folder it doesn't allow me to see the examplesHi,
for anyone having the Windows issue - there is a new release (build 2023-02-09) available that should fix it.
Actually the problem was the same as in 1.20.10 and related to the NWJS version:
krpano 1.20.10
At that time I had changed the NWJS version in 1.20.10, but unfortunately somehow forgot to apply that change also to 1.21...
Best regards,
Klaus
This post has been edited 1 times, last edit by "Suso Barral" (Feb 9th 2023, 11:05am)
if you run it from the main folder it doesn't allow me to see the examples
if you run it from the main folder it doesn't allow me to see the examples
This can be normal - please see here:
https://krpano.com/docu/localusage/#top
However, the strange thing is that version 1.20.11 does not give any problems and this new version, although it indicates the path of the content folder, does not allow it to be seen, I have also tried to put the testingserver inside the folder and it does not work with any browser, I'm going to check it again.
any update regarding chromakey video as layer? its long awaited demand.
And here another idea by using a krpano layer:
Chromakey Video as Layer
<layer name="move_circle" url="skin/move2.png" keep="true" align="leftbottom" scalechildren="true" scale="0.5" alpha="0.75">
<layer name="move_arrow" url="skin/move1.png" align="center" x="0" y="0" scale="0.5"
dragging="moveDrag()"
ondown="moveDown()"
onup="set(hlookat_moveforce,0); set(vlookat_moveforce,0);"
/>
</layer>
<layer ... url="floor.png" width="500" height="prop" scalechildren="true" ...
In previous versions, If dynamically changed the width, then the parent layers changed.
Now the parent layers do not change, but change when the scale changes.
Is it supposed to be like this?![]()
yes, here is an exampleIn previous versions, If dynamically changed the width, then the parent layers changed.
Now the parent layers do not change, but change when the scale changes.
Is it supposed to be like this?![]()
Do you have an example for testing/checking?
And please consider the notes from here.
![]() |
Source code |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
<style name="point" type="image" keep="true" url="red.png" parent="plan1" width="20" height="prop" /> <layer name="t1" type="text" align="top" text="onclick=switch(width,300,200)" /> <layer name="plan1" type="image" url="floor.png" align="top" width="300" height="prop" y="20" onclick=" switch(width,300,200)" scalechildren="true" /> <layer name="p1" style="point" x="50" y="70" /> <layer name="p2" style="point" x="100" y="100" /> <layer name="p3" style="point" x="150" y="150" /> <layer name="t2" type="text" align="bottom" text="onclick=switch(scale,1,0.5)" /> <layer name="plan2" type="image" url="floor.png" align="bottom" width="300" height="prop" y="20" onclick="switch(scale,1,0.5)" scalechildren="true" /> <layer name="p4" style="point" x="50" y="70" parent="plan2" /> <layer name="p5" style="point" x="100" y="100" parent="plan2"/> <layer name="p6" style="point" x="150" y="150" parent="plan2"/> |
This post has been edited 3 times, last edit by "San7" (Feb 10th 2023, 4:22pm)
Thanks - good example!yes, here is an example
That's just a warning when using very old textfield settings.I also noticed that when showtext.xml is connected, it gives a message in the console
WARNING: textfield 'border' is deprecated, use 'bgborder' instead.
That's a feature - see the noclip setting, but it shouldn't 'sway'...and when the text floats close to the edge, it starts to sway quickly, trying not to hide behind the edge of the screen