You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Arsdezi

Intermediate

  • "Arsdezi" started this thread

Posts: 174

Location: Ukraine

  • Send private message

1

Tuesday, April 1st 2014, 2:38pm

Little bug with text in Chrome browser (33.0 Win7) (SOLVED)

Hi!
I tested textfield plugin in FLASH and HTML5 versions and had bug with incorrectly determined devices attributes in the Chrome browser(Win7). For example:

<layer name="intro_text" keep="true" url="%SWFPATH%/plugins/textfield.swf" align="center" x="0" y="15"
visible="false" autoheight="true" background="false" border="false" enabled="false" scale="1.0"
html="data:text-intro"
css="data:css-intro"
textshadow="2"
onloaded="delayedcall(3.0, tween(alpha, 0.0, 2.5, easeInOutQuad, set(visible,false); WAIT(0); removelayer(intro_text); ));
if(device.mobile, mul(y,2));"
/>

<data name="text-intro" devices="flash|webgl">Text for Flash and WebGL support devices</data>

<data name="text-intro" devices="html5+css3d|ios"> or <..... devices="ccs3d" >Text for iOS and css3d support devices</data>

I had to change the attributes to: devices="ios|!webgl|!flash" and it's work correctly and displays the text you want!
PS: but is a not problem in iphone-ipad-simulator.html in Chrome when I was forced to turn parameter html5:"only+css3d"
*confused* *thumbup*
Panoreal — to make and see this wonderful world! *whistling*

This post has been edited 1 times, last edit by "Arsdezi" (Apr 3rd 2014, 11:05pm)


2

Thursday, April 3rd 2014, 11:29am

Hi,

the availability of WebGL (device.webgl) doesn't remove the availability of CSS3D (device.css3d).

Best regards,
Klaus

Arsdezi

Intermediate

  • "Arsdezi" started this thread

Posts: 174

Location: Ukraine

  • Send private message

3

Thursday, April 3rd 2014, 2:24pm

Hi, Klaus!

Then I do not understand what sense to specify them if Webgl = CSS3d?
For plugins and actions such determination HTML5 works well.
This means that we must attribute that to exclude from the device attributes?
!webgl or !css3d
*blink*

Thank you!

Panoreal — to make and see this wonderful world! *whistling*

4

Thursday, April 3rd 2014, 4:05pm

Hi,

when device.webgl is set, then WebGL is available and the pano will be rendered with WebGL.
When device.css3d is set, then CSS3D is available and can be used - e.g. the distorted hotspots were rendered with CSS3D.

Note - the krpano viewer itself and the plugins are also using the device object to get information about the device support.

And there are situations where WebGL is available, but CSS3D not (e.g. on some Linux systems).


What are you trying to achieve?
Detecting devices that don't support distorted projections - like when using CSS3D?
If yes, try: devices="!webgl+!flash" (that's the inverse from - devices="webgl|flash")

Best regards,
Klaus

Arsdezi

Intermediate

  • "Arsdezi" started this thread

Posts: 174

Location: Ukraine

  • Send private message

5

Thursday, April 3rd 2014, 11:04pm

Ok! I understood!

thank you Klaus for your advice!
*thumbup*
Panoreal — to make and see this wonderful world! *whistling*