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.

  • "John Myrstad" started this thread

Posts: 91

Location: Norway

Occupation: Product Specialist @ www.fuglefjellet.no

  • Send private message

1

Sunday, October 3rd 2010, 3:07pm

level based hotspots/plugins method

I`d like a method to show/create plugins/hotspots based on levels in multiresolution images. The events.onviewchange is using too much memory to populate a gigapixel image with detail hotspots/plugins

Typical usage scenario: Put plugin/hotspot info on 1000 houses in a gigapixel image of a city, which is only visible/created when zoomed in to a specified level. On a higher ( or is it correct to say lower? ) level there might be hotspot/plugins for streets/wards.

This post has been edited 1 times, last edit by "John Myrstad" (Oct 6th 2010, 11:51pm)


2

Wednesday, October 6th 2010, 8:03pm

How are you using onviewchange? Do you perform the hotspot manipulation every time the event is triggered? You could try implementing your own minimum interval system, such as a timestamp with the time of the last check (onviewchange would first check if it's been more than X seconds since the last check before doing the heavy stuff) or a plugin that checks the FOV every X seconds and then does the hotspot adding and removal from within itself... Where X is for example 1 second.

  • "John Myrstad" started this thread

Posts: 91

Location: Norway

Occupation: Product Specialist @ www.fuglefjellet.no

  • Send private message

3

Wednesday, October 6th 2010, 11:58pm

I`m just worried about overusing it since Klaus gave a warning in release notes:

Quoted

onviewchange
  • is called on every view change
  • note - this event should be used carefully, don't make "heavy" operations/changes here this events will be called every frame on moving

Similar threads