Sie sind nicht angemeldet.
krpano.com Forum »
krpano News »
News »Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
Mittwoch, 21. Februar 2018, 09:57
I've an issue with z-index and fullscreen.
In fact I use external div element out of the krpano div and I apply my own fullscreen treatment.
But since latests krpano version I've noticed that the z-index of the krpano element is applied to the highest zindex available (2147483647) and the others div cannot be displayed anymore with Android Chrome browser when rotating the screen (which apply the fullscreen event).
Is it a krpano or Chrome issue/feature ?
Mittwoch, 21. Februar 2018, 22:40
copyattributes()
Please note that the copyattributes() when Flash viewer does not copy all attributes to the new destination (mainly numeric) e.g. width, height, ath, atv.
The workaround: device.flash only set() function.
i played with copyattributes to copy all params from layer1 to layer2 and it turns out it has problems copying parent attribute: its value is correct in the debugvar but the layer doesn't show up in the parent element (it doesnt show up at all even if visible set to true)
Mittwoch, 21. Februar 2018, 22:49
I've an issue with z-index and fullscreen.
In fact I use external div element out of the krpano div and I apply my own fullscreen treatment.
But since latests krpano version I've noticed that the z-index of the krpano element is applied to the highest zindex available (2147483647) and the others div cannot be displayed anymore with Android Chrome browser when rotating the screen (which apply the fullscreen event).
Is it a krpano or Chrome issue/feature ?
https://krpano.com/docu/xml/#display.autofullscreen
Mittwoch, 21. Februar 2018, 22:53
Adding an ondoubleclick property for layer/hotspot as you did for events would be soooo nice!
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
<style name="doubleclick"
downx="0"
downy="0"
clicks="0"
onsingleclick=""
ondoubleclick=""
onclick="doubleclick_style_onclick();"
/>
<action name="doubleclick_style_onclick">
inc(clicks);
if(clicks == 2,
set(clicks,0);
stopdelayedcall(doubleclickdetector);
if((((mouse.x-downx)^2 + (mouse.y-downy)^2)^0.5) LT (device.touch ? 10 : 2),
ondoubleclick();
,
onsingleclick();
onsingleclick();
);
,
copy(downx, mouse.x);
copy(downy, mouse.y);
delayedcall(doubleclickdetector, 0.3,
set(clicks,0);
onsingleclick();
);
);
</action>
|
|
|
Quellcode |
1 2 3 4 |
<layer ... style="doubleclick"
onsingleclick="trace(-single click-);"
ondoubleclick="trace(-double click-);"
/>
|
Donnerstag, 22. Februar 2018, 20:32
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
<action name="break_test">
<!-- OK -->
trace( before break);
break();
error(AFTER BREAK);
</action>
<action name="break_test_1">
<!-- HTML5 & Flash goes to ERROR -->
trace( before break);
if( true == true,
break();
);
error(AFTER BREAK);
</action>
<action name="break_test_2">
<!-- loop break (the next iteration...) -->
trace( before break);
for(set(i,0), i LE 5, inc(i),
trace(i);
if( i EQ 2, break(); );
);
trace( 'loop broken at ', i);
</action>
|
Freitag, 23. Februar 2018, 00:31
Hi Klaus,
Please notice some break(); imperfection.
Neither in if( ) nor in for( ); loop is it doing as expected. Am I missing something?
Dienstag, 27. Februar 2018, 06:27
|
|
Quellcode |
1 |
<hotspot name="hs1" url="skin/Rons.jpg" flying="0" scaleflying="false" zoom="false" distorted="false" alpha="1" depth="off" /> |
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Scott Witte« (27. Februar 2018, 19:55) aus folgendem Grund: modified examples to include distorted and non-distorted version for comparison.
Dienstag, 27. Februar 2018, 17:36
There seems to be a bug with hotspot distortion in VR Mode in pr14. Distortion is always true. Here is the relevant code:
Zitat
Better, more natural non-distorted hotspot rendering for VR.
Improved non-distorted hotspot rendering for VR - the normal 'billboard' rendering method that is done on normal screens doesn't 'work' in VR. Now a rendering method will be used that will display the hotspots in an 'expected' way.
Dienstag, 27. Februar 2018, 19:51
The new method should be much better - in VR it should be the equivalent to the normal non-VR viewing.
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Scott Witte« (28. Februar 2018, 03:00)
Mittwoch, 28. Februar 2018, 10:16
In non-VR mode the distorted=false hotspots are oriented to the flat screen surface - but in VR mode there is no flat screen surface. In VR such hotspots look like they would rotate by itself when you move the head around. So they will not remain 'square' anymore (when viewing in the headset).Why is this important?
Feature Requests »
Zoom in webvr examples
(8. Oktober 2017, 22:28)
Textfield » interactivecontent ?
(18. Oktober 2017, 15:38)
News » krpano 1.19-pr13
(21. September 2017, 22:48)
krpano Panorama Viewer » strange triggering onover and onout on webgl hotspot
(1. November 2017, 17:46)
Mittwoch, 18. Oktober 2023, 21:39
Zum Seitenanfang
