Suchergebnisse
Suchergebnisse 1-20 von insgesamt 238.
I can also confirm this issue on Safari 14.0.2 (15610.3.7.1.10, 15610). On Safari 12.1.2 (12607.3.10) it still seems to work.
I recently worked with illustrator Tessa Schlechtriem on a (short!) experiment in storytelling. We wanted to explore a no-click interaction, and see if we could make a narrative respond to the viewer. http://tessascape.com/world/2017/war-worlds The old SightlineVR demo/experience "The Chair" from the Oculus DK2 era had an interaction mechanism that we really liked where you interacted with the scene just by looking around, and we wanted to try our hand at similar experience in an illustrated pan...
Quellcode 1 2 3 4 5 6 7 if(pressed, sub(dx, mouse.stagex, drag_stagex); if(dx LT 0, add(x, drag_currentx, dx); ); delayedcall(0, move(); draglayer(dragging) ); ); Or am I getting you wrong?
Well, isn't that a nice thing to do... (note: they are not required to share their fixes, but it would have been nice)
Hey, from the testcase it looks like the app does know the actual size (which makes me think that it should be possible to adapt a crop, but what do I know...)
Zitat von »klaus.krpano« For the application itself it's not possible to know if the image was downscaled or what its real image size was. Rats! Anyway, 1.17 is more stable for me than previous versions, so the "awesome" still stands. Looks like I chose a good path providing smaller imagery for mobile.
My wife and I have been experimenting with animated hotspots to get some "life" into a panorama. Animated frames are tiled into a single "filmstrip-like" image and a crop is dynamically applied, pretty much like the animated hotspot example (but a bit more advanced): http://files.fieldofview.com/temp/blinkie Here is one of the animation tiles: http://files.fieldofview.com/temp/blinkie/rose_01.jpg As you can see this is quite a large image. The technique works both in flash and html5 (in contrast...
Have you looked at my reply in your other thread? just upgraded to "november" version
The "auto" in embedpano has nothing to do with the "auto" in playsound. "auto" in embedpano means that krpano will make what it deems is the best choice between flash and html5 for your browser (and available plugin), whereas "prefer" always picks html5 if krpano thinks your browser can handle it (even if it thinks flash would be a better option). If you use "auto", krpano will pick flash for firefox, which can play back mp3. The "auto" in playsound means that krpano will automatically pick a na...
There are three js files: swfkrpano.js, krpanoiphone.js and krpano.license.js When you use the droplets to make a tour, it creates a single js file combining those three. This file you used before (named krpano.js). Now it seems you have renamed the new krpanoiphone.js to krpano.js and used it as is. That does not work because it is missing the contents of the other two files. Either you supply the 3 original js files and include swfkrpano.js in your page, or create a new krpano.js
We'll be back for the 5k mark. In a couple of weeks?
Aw... I missed the party...
While posting panoramic videos for Sziget 360 (http://sziget360.com/panoramavideo), I found out that when using Firefox the flashplayer would become extremely sluggish playing back panoramic video; scrolling the html page would be nearly impossible, and in non-fullscreen mode the framerate frequently became so low that Firefox suggested that the flashplayer should be closed. It turned out that by setting the wmode parameter to "window" (instead of the default "direct"), the video shows smoothly ...
Thanks for reporting this. I had some reports of the plugin causing a krpano error, but could not reproduce it myself. I will try to make the change in the following days.
This effectively means the end of the <tablet> and <phone> tags. That alone is something to celebrate
Congratulations! Thomas got there two days before you, but this is seriously impressive.
The short answer is "probably not any time soon"
There's some code here: double-click to "move to, center and zoom"
Zitat von »sachagriffin« Inputing "test" layer[input].text == "test" fails.. not sure if there's some EOL missing or added or what. Yes, that's probably it. If you have some time, could you check if it matters whether you set multiline to true or false?