Posts by zbooy

        set(uniqname, azimuthline);
        addhotspot(get(uniqname));
        set(hotspot[get(uniqname)].point[0], ath = get(hpos), atv = (image.vfov/2));
        set(hotspot[get(uniqname)].point[1], ath = get(hpos), atv = (-image.vfov/2));

When adding a polyline hotspot like shown above, the resulting line is drawn in the wrong place, with some vertical offset. The code worked fine in 1.21. It is broken as well if using JS code.

Well, I have found the answer myself and I'm posting it here for anyone having this problem in the future Actually, it turned out to be trivial: just use the view.fovmin variable, it gets constantly updated even if not set initially.

Hi,

I am setting the maxpixelzoom attribute for the view element in the xml. How can I calculate the (s|h|v)fov for this maximum allowed zoom in the current window size other than by zooming in, getting the fov, and then zooming back out?

Hi,

on my website the 03-30 update causes the HTML content of child text layers of a hotspot to magically disappear if they are far outside the starting viewport. The 02-09 version works fine.

It probably has something to do with the "pixel-exact visibility check for the flat/2d'-hotspots" mentioned in https://krpano.com/forum/wbb/inde…&threadID=19253. Funny thing is that it's only the HTML content that is gone, the background part is properly sized and visible! (See the attached pic.) When inspecting with the DevTools the innermost divs are no longer there.

Quote from klaus.krpano

Quoted from "San7"
and when the text floats close to the edge, it starts to sway quickly, trying not to hide behind the edge of the screen

That's a feature - see the noclip setting, but it shouldn't 'sway'...

I have just noticed this too: with noclip="true" the showtext plugin calls showtext_do_clipping() many times per second resulting in text switching position to and fro.

Thank you, krpano.get('%1') was the way to go.
Version 1.21 indeed seems to be noticeably faster on a scene with lots of text hotspots.

Hi,

actually I did change some js() calls into jscall() but what about the ones using action arguments, like
js( console.log(get(%1)); );
?

Hi,

I have just tried updating my site to v1.21 only to find out that js() calls from xml no longer work.

js( console.log(1) ); does nothing
js( "console.log(1)" ); as well

while jscall( console.log(1) ); works fine

Quote from klaus.krpano

in krpano version 1.21 it will be possible to access the original JS Events object

Thanks Klaus, that's really awesome news. Waiting for this new release then

Hi,

thanks for your detailed help. Actually I was hoping for some flag inside the onclick handler, just like the native JS mouseEvent. Monitoring shift key presses might not always work: for example, what if it's pressed while the browser window does not have the focus and only then the hotspot is clicked?

Hi,

I'm trying to detect if shift (or ctrl/alt) key is down when a hotspot is clicked. Is there any away to get at the JS mouseEvent shiftKey property?

Some of these paths seem to be available as variables:
network.viewerpath
network.htmlpath
network.firstxmlpath
network.currentxmlpath

so ....get('network.firstxmlpath') should work.

Ah yes, now there is a native ondoubleclick event so no need for the plugin. Removed; thanks for the suggestion

Thank you very much, this did the trick!

It is certainly stated in the docs:
<krpano>
This is the main / root element of a krpano xml file.
All further xml elements need to be defined within this element.

Although it seems this was not enforced until pr15 version.

zbooy

Hello,

I have just tried to do the upgrade from pr14 to pr15 but without success.
I'm including a config file in my xml, like this:
<include url="list.xml" />
The included file is loaded from http://zbooy.pl/giga/list.xml and looks like this:

<panoramas>
<pano name="wysoki-wierch-zachod" title="Wysoki Wierch" />
<pano name="waksmundzki-wierch" title="Waksmundzki Wierch" />
[.......]
</panoramas>

It's just a basic config file that worked just fine until today; now it stops with the XML parsing error.
The file passes XML validation, of course. If I omit the include, everything else is OK.

I have reverted krpano,js to pr14 and everything is working again. Any ideas?

zbooy

I'm having the same problem :(  
Loading eg. http://panoramy.zbooy.pl/360/show.html?…zyz&lang=e&t=32 and switching to fullscreen via right-click menu kills my Firefox instantly. Beta 7 was OK and beta 8 is not. The quickfix version is crashing as well.

zbooy
http://panoramy.zbooy.pl

Quote from Amedee

I just came across something funny with the trace function: when invoked from the 'onload' event handler, it issues the whole event code instead of just the parameter.

Code

onstart="trace(onstart);lookto(100,20,80);"

Will print

Code

trace(onstart);lookto(100,20,80);

Looks logical to me - after all, you assigned the string "trace(onstart);lookto(100,20,80);" to the onstart variable... :)

zbooy
--
http://panoramy.zbooy.pl/