Posts by philippeK

Hello,

Last decade Web has changed significantly: flash and IE are dead, WebGL 2.0 is broadly supported by all browsers, WebGPU & WebXR are on the way, JavaScript evolved a lot, WebAssembly has arrived, etc.

I use Krpano for one of my client in France and I'm curious klaus.krpano how do you see the future of Krpano ?

The only forum thread I've found with examples is here: MAKE OBJECT (MULTIRES) droplet

But it doesn't work for my example, which is:

<image type="flat" frames="2" frame="1">
    <flat url="frames/out-%00f.jpg" />
</image>

It just shows a black screen and the browser actually didn't make any request for any images. However the files frames/out-001.jpg and frames/out-002.jpg exist and the following works well:

<image>
    <flat url="frames/out-001.jpg" />
</image>

I have no idea why the example with frames doesn't work.

Hello,

There is section in the doc that mentioned the frames and frame attributes of <image>: https://krpano.com/docu/xml/#image.frames

But I was unable to find any other examples nor description on how to use it. I've also spent some time on the forum, but no information on that neither.

Use Case: I want to show a Hyperlapse (composed of 125 flat JPG images) with scrolling slider which loads different images based on its direction.
Problem: I've first tried loadscene, but it doesn't look like a good solution for this, because could not rid of black screen between scene switching.

So I run through images.frames and it looked like a good feature for my use case. But I failed to make it work (not even the first frame, just black screen).

Does someone has a code example on how to use it?

Thank you Hellkeeper for such a super quick response .

But I've found another solution rather than adding more memory.

My VM didn't have any Swap file, so I think when krpanotools reached the limit of memory it tried to use a swape file, but none was available.

Here is the guide that helped me to resolve this issue: How To Resolve "Out of Memory" Errors on Ubuntu 17.10. It also worked for my VM (Ubuntu 20.04).

I run the `krpanotools makepano` script on a VM in a cloud.

The command `./krpanotools transform -meminfo` gives this:

totalmem:  1682 MB
availmem:  1057 MB

and `./krpanotools transform -memtest` this:

...
...
...




totalmem:  1682 MB
availmem:  58 MB
freespace: 218 MB
allocated: 1336 MB


totalmem:  1682 MB
availmem:  53 MB
freespace: 214 MB
allocated: 1340 MB


totalmem:  1682 MB
availmem:  50 MB
freespace: 210 MB
allocated: 1344 MB


Killed

Hellkeeper have you resolve your problem?

Thanks Klaus That helped.
I've just adapted the following code from Postprocessing Demo: Popups with Background-Blur :

// enable browsed-based mouse-wheel and touch-scrolling support:
div.addEventListener("wheel", stopPropagation, true);
div.addEventListener("mousewheel", stopPropagation, true);
div.addEventListener("DOMMouseScroll", stopPropagation, true);
div.addEventListener("touchstart", function(event){ if(krpano.device.ios && window.innerHeight == krpano.display.htmltarget.offsetHeight){ /* avoid the iOS 'overscrolling' for fullpage viewers */ var bs = document.body.parentNode.style; bs.position="fixed"; bs.top=0; bs.left=0; bs.right=0; bs.bottom=0; } krpano.control.preventTouchEvents = false; event.stopPropagation(); }, true);
div.addEventListener("touchend", function(event){ krpano.control.preventTouchEvents = true; event.stopPropagation(); }, true);
div.addEventListener("gesturestart", preventDefault, true);

I struggled with a bug/behavior in <layer> tag on touch devices. I have the following XML structure:

<layer name="infocard_container"
  type="container"
  handcursor="false"
  parent="STAGE"
  capture="true"
  bgcapture="true"
  maskchildren="true"
  keep="true"
  width="340"
  height="100%"
  x="0"
  y="0"
  alpha="0"
  autoalpha="true">
    <layer name="infocard"
      url="%$assetsUrl%/plugins/custom/infocard.js"
      width="100%"
      height="100%"
      enabled="true"
      capture="true"
      bgcapture="true"
      children="true"
      maskchildren="true" />
</layer>

In url="%$assetsUrl%/plugins/custom/infocard.js" plugin I create an HTML element which must be scrollable. Scroll works well with a mouse, but doesn't work on touch devices like mobile or laptop with touch screen.


I've tried different variations of CSS rules (overflow: scroll, very high z-index, touch-action etc.), <layer> attributes (capture, bgcapture etc.), scrollarea plugin, but neither works. However the "touchstart", "touchmove" events on my custom element work well, so that means that no html parent element calls `e.stopPropagation()`. So I did not figure out what prevents touch scroll from working.


Does someone has any idea about it?

I was wondering how can I specify a custom plugin location. Here is my use case:

• Main XML config file is stored in a database and loaded at run time via
  
  Code

  loadxml

  and not via

  Code

  xml

  object attribute of the

  Code

  embedpano

  function.

• Then this XML config includes a few others XML config stored as static assets on the host.

When I add

<include url="add_hotspot/plugins_l/add_hotspot.xml" />