• Hi,

    I have uploaded a new 1.0.8 beta 8 version - build 2009-06-09,

    there a new possibility for 'fly-out' hotspots was added:

    <hotspot> has a new parameter - "flying":

    • possible values are from 0.0 to 1.0 (for dynamic tweening)
    • 0.0 = normal view
    • 1.0 = makes the hotspot independent from the panorama rotation and scaling (= locked to screen)

    here is a example:
    HTML: https://krpano.com/examples/108b8…ots/flyout.html
    XML: https://krpano.com/examples/108b8…pots/flyout.xml

    here the relevant code:

  • See what I said you are a machine!!!!, GREAT update :) I don't really use the flyout that much, but I am sure it will come in handy, and now oficially Krpano is WAY better than FPP (not that it wasn't before) I know its not a race.. but if it were, you'd be ahead now :D

  • Hi Klauss!

    Reading your code raises 2 questions...

    First, you are using backup_* parameters in your hotspot definition. Are these real hotspot parameters, or can you actually bind any variable to a hotspot? (This might be interresting to define hotspot or plugins variables/properties...)

    Secondly, your flyout/flyback actions do specify a 'scope' for the variables -- I would have expect to see something like 'hotspot[spot].rx' and not just 'rx'...
    There seems to be some inheritance; how does this work and how can we differenciate between a 'local' variable with the same name?

    Thank you in advance for the clarification.

  • Klaus, this functionality is fantastic, I was only thinking of asking if something like that is possible and here it is done.

    Your commitment to ongoing development is astounding.

    Great work.

    Liverpool based panoramic photography, virtual tour and
    web media organisation specialising in high quality web experiences.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!