1.0.8.14 pre-release / release-candidate

Hi Klaus

Can we have somme documentation for this

Zitat

* new actions for looping / repeating actions:
- for(startaction, condition, nextaction, loopaction)
- asyncfor(startaction, condition, nextaction, loopaction)
- loop(condition, loopaction)
- asyncloop(condition, loopaction)

Thanks a lot

Thanks a lot Klaus

Wow Klaus! Thanks! The for loops will save alot of headaches in future projects!

Im still not sure what asyncfor does though...

what loop would fit if you try to do a loop over an array?
something like this?

<pictures>
   <pic name="p1" url="image.jpg" />
</picture>


<action name="add_pictures">
  for(set(i,0), i LT pictures.pic.count, add_pic(i));
</action>
<action name="add_pic">
 addplugin(pictures.pic[%1].name);
 set(plugin[pictures.pic[%1]].url, pictures.pic[%1].url);
</action>

or should i use the asyncfor?

The difference between "for" and "asyncfor" is that in a "for" loop, krpano first executes all iterations of the loop before continuing with the rest of the actions, whereas when you use "asyncfor" instead, krpano only does one iteration at a time, all the while executing other actions.

So "for" blocks execution of all other actions and events until its done, while "asyncfor" does not. You would use "for" for smaller loops, where it is important that every iteration gets executed before krpano continues. On the other hand you would use "asyncfor" for relatively long loops that would otherwise lock up krpano for too long.

In your simple case, either would work.

I tried something out quickly:

<picture>
		<pic name="test_1" />
		<pic name="test_2" />
	</picture>
	<action name="add_menu_items">
		for(set(i,0), i LT picture.pic.count, inc(i), test(i));
	</action>
	<action name="test">
		txtadd(test_name, 'plugin_', get(picture.pic[%1].name));	
		set(testvar, %1);
		trace(%1, get(picture.pic[%1].name), get(test_name)); <!-- not working -->
		trace(get(picture.pic[0].name)); <!-- working -->
		trace(get(picture.pic[get(testvar)].name)); <!-- not working -->
	</action>

why is the 1st and 3rd not working in the test action?

Ok, and I reckon that in your example, trace already has something build in to convert 1 to get(i) automaticly, and if i doesnt exists it just traces i?

for(set(i,0), i LT 10, inc(i), trace(i));

can't that be the default behaviour of actions too? or is this because of some backwards compatibility?

Hi,

I've built a tour for all devices with the 1.0.8.12 template. Iphone 4 loads tablets tiles.

So, i've uploaded the 1.0.8.14 release candidate 2 viewer to get the krpanoiphone.js which increased iPod4 stability by limiting and automatically downsampling the max. cubesize to 640x640. Then i replaced the old krpanoiphone.js and .swf (version.12) with the new ones.
I built my tour once again with the .12 Vtour template and the new .js. Uploaded only the .js .swf and .html on the server (not the xml). I've just tried, and it seems that iphone still to get the tablet tiles..!?
Link for iphone or smartphone

I've made it wrong ?

Thanks.
Steph

I think I found a bug. On version 1.8.0.14-rc3, none of the "InOut" tweens seem to be easing out, only easing in. Let me know if you can't reproduce this and I'll upload an example.

Thanks

Oops, just read on the release notes that they were removed on purpose. Is there some way to get them back? I use them a lot for "non-blocking" camera control

Hi emediquei,

Yes...

Zitat

krpano 1.0.8.14 viewer release candidate 3 (2011-05-20)

Changes/Fixes (compared to the last pre-release from 2011-04-11)

# krpano.swf & krpanoiphone.js

* new actions for looping / repeating actions:
- for(startaction, condition, nextaction, loopaction)
- asyncfor(startaction, condition, nextaction, loopaction)
- loop(condition, loopaction)
- asyncloop(condition, loopaction)

* new Math object for mathematical constants and actions:
- Math.PI
- Math.abs(var) or Math.abs(result,v)
- Math.acos(var) or Math.acos(result,v)
- Math.asin(var) or Math.asin(result,v)
- Math.atan(var) or Math.atan(result,v)
- Math.atan2(result,a,b)
- Math.ceil(var) or Math.ceil(result,v)
- Math.cos(var) or Math.cos(result,v)
- Math.exp(var) or Math.exp(result,v)
- Math.floor(var) or Math.floor(result,v)
- Math.log(var) or Math.log(result,v)
- Math.max(var,var2) or Math.max(result,...vars)
- Math.min(var,var2) or Math.min(result,...vars)
- Math.pow(var,var2) or Math.pow(result,v1,v2)
- Math.round(var) or Math.round(result,v)
- Math.sin(var) or Math.sin(result,v)
- Math.sqrt(var) or Math.sqrt(result,v)
- Math.tan(var) or Math.tan(result,v)

* Removing of all InOut and OutIn tweentypes - they were typically not
needed and the removing saves a lot of swf and js filesize.

Alles anzeigen

I feel that is for let the player as small as posible ... Surely due to the adding of the looping actions and maths features...
That makes me think that if it could not be more adequate making the player light and the enhanced features as external files (included files) instead of making an compromise between features and lightweight... Don't you think so ?

SAlut.

I agree that these tweens are not very used. I've also only used InOutQuad for custom camera control. Here are a couple of examples:

http://demo.digisfera.pt/segourmet/
On this website made in krpano, the user can click links on the "Produtos" section. I wanted to allow the user to click while the camera is moving, and since "lookto" blocks user control, tweening "hlookat", "vlookat" and "fov" seemed to be the best solution. easeInOutQuad allows the movement to be smooth both in the beginning and the end.

http://www.digisfera.pt/maior-fotografia-lisboa
In this gigapixel there is a custom movement: the camera zooms out and then zooms in. You can see it by clicking on a couple of thumbnails. Once again, InOutQuad allows for a smooth beginning and end of movement.

I tried replacing Quad by Cubic in both cases, and Quad resulted in a more adequate acceleration. So, I think the best solution is what you sugested:

- Make all tween types available in a separate plugin
- Just keep 1 or 2 of these types in the "core", and map all others to them. Probably print a warning whenever the mapping is needed.

A more powerful lookto() would also be a solution and a nice feature. I think it would be cool to have a new lookto() function which provided:
1. non-blocking mode
2. ability to set initial and final speed (to create more complex movements with consecutive calls to the function)
3. a "donecall" parameter, like in tween() (as a way to support consecutive calls to the non-blocking function)
4. a way to define our own motion type functions

Thanks a lot!

Thanks Klaus! Can't wait for it :)

I use the 2011-04-11-krpanotools-1.0.8.14-win beta version to create a vtour in combination with the 2011-05-20-krpano10814-viewer-rc3 beta version. This is working fine for the pc, but when I try to use the combobox for ipad, I get an error message: combobox plugin - too old krpano version (min. version 1.0.8.14 / build 2011-05-19)

<krpano version="1.0.8.14" onstart="startup();">
<!-- vtour.xml template krpano tools version 1.0.8.14 -->

How can this be? Am I confusing something?

Michael