krpano 1.16

Hi,

Quote from izoneguy

I downloaded the new version - but it was only the tools?

How do you mean with 'but it was only the tools'?

Quote from izoneguy

I had a 1.8.15 project with tooltips.Now they don't work in 1.16.3

Quote from zappano

Same problem, not more tooltips when using html5 and MAKE VTOUR (NORMAL) droplet.bat (1.16.3).Could you please help Klaus?

Note - since version 1.16 the NORMAL droplets set html5=prefer instead of html5=auto in the html files!
This means the HTML5 viewer will be preferred when both - Flash and HTML5 - are available.
And in the HTML5 viewer there is no 'showtext()' action - so the tooltips via showtext() will not work there - they will work only in Flash.

In one of the next releases the showtext() usage in the vtourskin.xml will be changed to tooltips that will work like in the tooltips example:
https://krpano.com/examples/116/e…ml?html5=prefer
This way they will work in Flash and HTML5.

Best regards,
Klaus

Hi,

Quote from Aperol

i tested it on my tablet samsung galaxy tab2 with android 4.1.2 with the native browser and the gyro plugin is still enabled. only on firefox browser is disabled.

I would say this is impossible!
Make sure that the vtourskin.xml from 1.16.3 is uploaded and also clear the browser cache to make sure that it will be loaded.

Best regards,
Klaus

Quote from PistaJ

How do I add the full screen button on android devices?

The xml is there in the skin but it is not working on 1.16

Hi,

at the moment there are no Android browsers that are supporting the HTML5 fullscreen mode.

Best regards,
Klaus

Hi,

I don't have a GT-P7500 for testing, but a GT-7510 with Android 4.0.4 (should be the same device but Wifi-only) and I can't see any differences between these two links. They work the same but often let the browser fall back into the buggy css3d-software-rendering...

Quote

with Android 3.2 on navite browser = black screen

Just a black screen without any error message?
That should be normally not possible. A Android 3.2 device should either display the Flash version or shown an error that the browser isn't HTML5 compatible...

Btw - keep in mind that the Android stock browsers (and all other WebView-based browsers) are very bad regarding CSS3D support and they will be not longer developed by Google. I would hardly recommend using Chrome, Opera Beta or Firefox on Android. In these browsers you links are working very fine (especially Android Firefox displays and performs very well).

Best regards,
Klaus

Hi,

Quote

my big issue is that normally the users are noobs.. people just use the browser that is already installed in the device instead of search and install a new app of a browser..

I know of course, but the Android stock browsers are just this fundamentally bad, that there are real fixes not possible. Keep in mind that the Android stock browser has very buggy memory management, so that one time the pano might work and next time not because there is no enough free ram - by installing additional Apps like 'Cool Tool - system stats' this behavior can be good monitored.

The only REAL solution will be probably time and newer Android versions and devices where the current Android WebView will be replaced by Chrome WebViews.

Quote from Aperol

is there a way to avoid the css3d bug in the last version of krpano 1.16.3 with android on native browser?

Which bug exactly do you mean?
Can you describe it detailed, maybe with screenshots or videos?
There should be no CSS3D specific bug in krpano 1.16.3 - the HTML5/CSS3D output from version 1.16.3 is EXACTLY the same like in 1.16.1!

If you want to avoid the fall back into software rendering you could try using smaller images, but then this will affect also newer and more powerfull Android devices...
e.g. try:

<display hardwarelimit="256" devices="androidstock" />

Best regards,
Klaus

Hi,

Quote from spelican

I found some strange thing maybe somebody clear it out.
i've placed krpano-1.16.3 folder on local server (Denver) to see and check examples files. Demotour-corfu tour.html works fine, but tour_html5.html have errors - ERROR: ../../../plugins/scrollarea.js - loading failed! (undefined) and ERROR: ../../../plugins/bingmaps.js - loading failed! (undefined) and ERROR: ../../../plugins/bingmaps.js - loading failed! (undefined) but pano itself works fine.
HTML5 is working on lokal server but why this problem with pathes?

Please check all paths and test if the files are accessible. From krpano side there should be no problem here.

Quote

i tested again the virtual tour on the tablet Samsung galaxy tab 10.1 with android 4.0.4 (the last available) of my friend (tour made with krpano 1.16.3 ), i opened it with android browser:

What you see is the buggy tiled-based rendering of the Android WebView-based browsers. It happens when the browser has too low memory. There is no real way to detect it or to avoid it.

As Tuur already said - use Android Chrome or Android Firefox - these browsers are newer and better and don't have that 'bug'.
Or wait for Android 5.0 or Android 6.0 where Google will hopefully have replaced the current WebView with a Chrome-based one .
From developer point-of-view there is currently no possibility to let all kind of tours automatically work in WebView-based browsers on ALL Android devices. If you want to avoid that situation you could detect that browsers by the 'androidstock' devices setting and then just show a message that a different browser should be used...

Quote from Aperol

i don't know why it can run without any issue a tour made with krpano 1.16.1 , and not with 1.16.3

Was the tour exactly the same when testing, comparing?
Same memory usage?
Same free device memory when testing? (The free memory can be shown in the top-bar by apps like 'Cool stats')
E.g. already one additional thumbnail can cause hitting the browsers memory limit and so that bad rendering.
The krpano CSS3D rendering itself is the same in 1.16.1 and 1.16.3 and can't make the difference.

Best regards,
Klaus

Hi,

Quote from Nomis

I set it on true on tour.xml and vtourskin.xml. On the tour_editor.html it works fine but on tour.html it does not show up. Nothing else was changed. I use Firefox. Any idea about that?

In the tour.html the embedding setting html5=prefer is set by default - that mean when opening the tour.html in Firefox probably the HTML5 viewer was used - the tour_editor.html on the other side has set html5=never, which means that it will always use the Flash version.

And in HTML5 the showtext() action, which was used by the tooltips, is not supported - and that means the skin tooltips are currently working only in Flash.

Quote from Nomis

to let them pop up i tried to ad "onover="skin_showthumbs()" at the end of the

The skin_btn_thumbs button is loading the attributes from the 'skin_glow' <style> element - and there the onover event is already set - that means the onover event from the style will overwrite your onover event.

Here a way for simply extending the skin_glow <style> for an optional additional onover code:

1. add a check for the existence of an 'onover2' event - and if its there - call it - e.g. here the red code:
   <style name="skin_glow"
   ...
   onover="if(skin_lockglow === null, copy(skin_lockglow,name); skin_buttonglow(get(name),0.3) ); if(onover2, onover2());"
   ...
   />
   
2. then as second step - simply add an onover2 event to the button:
   <layer name="skin_btn_thumbs" ... onover2="skin_showthumbs()" />
   

Best regards,
Klaus

Hi,

it seems you were talking about Android Flashplayer issues...
Especially Flash+Firefox on Android are not working well, but these problems are not directly related to krpano...

I'm already thinking about letting the embedding script always prefer HTML5 on Android by default, regardless if the Flashplayer is installed or not...

About your 'EDIT2' description - which browsers have you tested?
I don't have a Galaxy S2, but several other Android devices (TF700T, Lifetab S9512, Galaxy S3, Galaxy Tab 10.1, Nexus S and Nexus 7) and the html5 viewer is working on all of these devices...

Btw - I think the best browser for Android is currently Android Firefox 22 (currently Firefox Beta) with enabled WebGL - in this Firefox version Mozilla has dramatically improved the WebGL performance (there will be soon also a new krpano release where WebGL will be prefered automatically for these Firefox versions).
E.g. test this link in Android Firefox 22:
https://krpano.com/krpano.html?xm…l5=prefer+webgl

Best regards,
Klaus