Hi,

there is a new (pre-)release:

krpano version 1.0.8.15:
This version is mostly a bugfix version of the 1.0.8.14 version, but it also includes some important internal architectural changes in the HTML5 viewer, that should improve the deep/z-ordering of distorted hotspots and also make them better 'click/touch-able'.

Download the latest pre-release here:
http://krpano.com/download/beta/#2012-06-03

See the list of all changes in 1.0.8.15 here:
http://krpano.com/download/beta/#2012-06-03
http://krpano.com/download/beta/#2012-05-04
http://krpano.com/download/beta/#2012-04-24

Why a pre-release?
There are still some things left that need to be changed/fixed, e.g. some tools settings, some plugin features, smaller internal changes and this will still need some time, but the new changes, especially in the html5 viewer and regarding distorted hotspots are worth to be tested.

Best regards,
Klaus

Hi,

thanks for the report and the video!
I'm already aware about that problem and working on solutions, Nupsi was posted here also about a problem with that version, that the problem there is the same like here.

The problem in detail:
In the older krpano versions the plugin and hotspot elements were placed internally in different html layers (simple html div elements), but in the new version they were placed together into one layer to solve the Safari click order problems with the distorted hotspots. But that seems to disable the Safari internal hardware acceleration when drawing the hotspots in some situations. And without hardware acceleration the rendering performance breaks down and causes the described behavior.

In my own tests this problem doesn't occur. I'm not sure why and when exactly Safari stops using the internal hardware acceleration, but I will try to find out and also restore the old way of ordering plugin and hotspots into different html layers. That internal change was also a reason for doing that pre-release to find out such problems.

The next version (a pre-release again) should be ready during the next week.

Best regards,
Klaus

Hi,

there is a new pre-release of the 1.0.8.15 version:
http://krpano.com/download/beta/#2012-05-04

• It fixes the 'performance problem' with hotspots from the previous pre-release. In fact it was not a krpano bug or real performance problem. It was a 'rendering / screen updating' bug from the Safari browser. A simple internal workaround by changing the HTML structure a bit fixed that problem.
  
  
• With this new version it's possible to show distorted hotspots above normal hotspots, e.g. necessary for 'fly-out-hotspots'. But due some system limitations it is not possible to sort/order normal hotspots and distorted hotspots automatically. To solve this, there is the a 'zorder2' setting for normal hotspots. By using the zorder2 setting it is possible to define if a normal, non-distorted hotspot should appear above or below the distorted hotspots.
  
  
• Distorted hotspots behind the viewing plane (=rotated behind the view) should be normally not clickable, but due a Safari Bug they are sometimes still. To solve this there is a new automatic workaround that disables these hotspots automatically when they are behind the view and re-enables them when they get visible again.
  
  
• As new feature there is now the full and exact support for horizontal viewing range limitation. The simple and not very accurate xml workarounds are not necessary anymore.
  
  
• For all other changes / fixes please see the link above.
  

Zitat von »HansNyb«

Another thing related. Please read my report about the airplay problem.
http://www.krpano.com/forum/wbb/index.ph…d&threadID=7191

About the Airplay problem - I have added the 'x-webkit-airplay=disallow' and 'airplay=disallow' settings like suggested in the Apple docs, but they are not working and seemed to be ignored. That might be an Apple bug, I have found also some other reports on the web that this is not working...

Zitat von »Tuur«

Has that anything to do with this problem aswell?
http://www.krpano.com/forum/wbb/index.ph…d&threadID=7166

No, there is no relation between these problems - on iOS preloading audio or video is not possible. For that reason the krpano soundinterface plugin itself also ignores the preloadsound() actions at the moment.

Zitat von »image360«

iPad 1 and soon 2 are basically already dead ends. To even try and support them is a complete waste of time

I have to disagree here - the iPad 1 and iPad 2 are still very useful devices and I will still try to support them (and older iOS versions) as good as possible to let krpano run there also as good and as stable as possible!

Best regards,
Klaus

Hi,

Zitat von »sachagriffin«

Were the overriding tags fixed in the js version?

yes!

sorry, I have totally forgotten to mention that
I have added that now too to the news/changes list:

Zitat

Fix: The overriding of <plugin> and <hotspot> attributes by redefining wasn't possible when keep="true" was used.

Best regards,
Klaus

Hi,

Zitat

Not sure what you mean with behind viewing plane.

The expression 'viewing plane' is from 3D graphics - there it defines the 'near plane' of the viewing frustum (here an illustration about that). When an 3D object (the distorted hotspot) is behind that plane, it is not visible and should be not click/touchable in any way - but the Safari browser has a bug there because it projects the click/touch-area for these elements sometimes in front of that plane on the screen and so they were click-able even if they weren't really on screen.

Sacha Griffin describe that problem here as '180 degree doppelganger hotspots' problem :
Out of view Distorted Hotspots to be disabled automatically.

And this new release fixes that Safari bug by calculating if the hotspots are behind that viewing plane and by automatically disabling them in this case.

Zitat

I can see that they still react behind a textfield with an image above it.

Hmm... not should not happen anymore...
You mean a textfield with a html image inside that textfield and when a (distorted?) hotspot is behind that imaged, then the hotspot still reacts on clicks?

Zitat

Another problem I have seen is that with larger resolution the hotspots all start moving during autorotation.
There is no problem with manual panning.

The limit seems to be around 1920x1080 on my iMac 27". At full resolution 2560x1440 they can move 5-10 pixels.

That's strange, there is technically no difference between 'normal panning' and autorotation...

What exactly do you mean with 'start moving' and where to they move?
And do you mean normal hotspots or distorted hotspots?
And what zorder settings where used in this test?

Best regards,
Klaus