Suchergebnisse
Suchergebnisse 1-5 von insgesamt 5.
Zitat von »indexofrefraction« when a style is applied to an element (i.e. hotspot) all its attributes are copied to the target, except for attributes already set on the target. there is no unloadstyle() because it is impossible to know what was set on the original hotspot after this procedure. but to go back to the original state you could maybe backup and restore your hotspot something like... copy(hotspot[example_bak], hotspot[example]); set(hotspot[example_bak], visible, false); hotspot[exam...
Hi there, How can I unload <style> added to <hotspot> dynamically? When I assign style to hotspot I use Quellcode 1 hotspot.loadstyle( @style_name@); method, but how can I remove/unload this style without deleting or replacing hotspot itself? Thanks, looking forwad to get reply from you. Regards, Maksim
Hi, Let me explain the situation itself. We make an SPA where a couple of pages depends on krpano plugin, so we use Webpack to manage JS bundle. If I decide to switch off --use-strict mode for all imported dependencies at may leed to future errors. So, I hope that this behaviour will be fixed in future releases. We use krpano files itself to give users ability to manage hotspots that they have built in Panotour (icons, position etc) Regards, Maksim
Klaus, Thank you for your suggestion, but unfortunately it doesn't solve my problem. Did you have a chance to check out the link that I've attached to the post? The problem still exists whenever I put 'use-strict' mode, and it's only disappears when I remove 'use-strict' definition from JS file. Could you please, check out error example link and suggest another solution?
Hello there, I've come across with initialization Krpano Viewer Error while setting "use-scrict" mode in Javascript. I can't just switch it off because too much functionality depends upon this mode in other modules. To represent this Error I've built a codepen example (https://codepen.io/anon/pen/LmBPvm )-> open developer console to see the Error message. According my observations it happens due to setting Uint8Array.length = 0, when in 'strict mode' assignment to read-only properties is not all...