krpano 1.19-pr14

Quote from klaus.krpano

Sure - it's a Chrome bug - see these threads for more information about updated plugins:
Possible gyro issue with Chrome 65 for Android.
Webvr not working with Chrome's latest updates

Thank you so much, Klaus ! You're the best ! Cheers

You can download Chrome Canary for the moment to get it working.

Quote from maksjm

Hello Klaus !

I've noticed that since the last Chrome update ( 65 ) the gyroscope is not working anymore on my Samsung smartphone.

http://www.prismamediaxrlab.com/tour-de-france/

Quote from indexofrefraction

i also never understood break();
long ago i tested it and i failed to use it to exit an action on a condition.
since then i never used it again.

Just a simple code for demo

for(set(i,0), i LT 2000, inc(i), 
	if(scene[get(i)].name, 
		error(i);
		,
		error('no more scenes');
		break();
	);
);

you can check it will stop once the condition is not true anymore, and then you will avoid looping until 2000

the docs say:
"Break / stop the execution of the current actions call."

now, the problem is that break() only breaks the actual block
this works for loops, but you cant use it in a condition to exit an action.

<action name="test" autorun="onstart">
 		if(true, break());
 		trace('a')
		break();
 		trace('b');
	</action>

INFO: a <--- this should not happen
note: the 2nd break() works, 'b' wasnt logged

strangely it works in the condition in your example....
so i guess either there is a bug or "stop the execution of the current actions call" is not meant how i understand it

it would be nice to have a return(), even if it is not used for a return value. could be called exit() ?

Hi Klaus,

Having a hard time understanding the new hotspot math in WebVR mode. For example, I place the scene title in a non-distorted text hotspot at the top of the stage. In non-vr mode and in pre pr14 releases that is easy: oy = stageheight/-2. But in true WebVR mode (simulated works much differently) in pr14 I can't figure out what is going on. What is the formula?

If you want to see my various attempts I will post them.

Quote from klaus.krpano

I will think about it, maybe as exitcall()...

that would be great
it just would allow nicer code by avoiding big condition blocks sometimes

Quote from klaus.krpano

I will think about it, maybe as exitcall()...

It would be great.

Piotr