GeoK,

As you can see the post, the hotspots are generated on-the-fly when scene is created. (Pro: same hotspotnames for different scenes, loading Just In Time).

Apparently I will face to the same issue and I see following scenarios:
a) create my own xml tag with hotspot attributes and scenename and load the particular hotspots on the onstart event of the scene;

b) create all hotspots outside the <scene /> tag and add the attribute scenename=parent_scene to each hotspot. On onstart event of the scene just set enabled=true for the hostposts where the scenename=currentscene.
(Cons: performance and memory issue when big image hotspots).

Has anybody a better idea?
Thank all of you,
Pavel

you need to understand that :
- you can access all scene properties by scene[x].property
- but there is only one scene content active at a time

that means you cannot access the hotspots defined in any scene,
only the ones of the active loaded scene.

so either you parse all scenes xml manually by using scene[x].content
or you build your hotspot information as an array outside the scenes,
and then add them dynamically onxmlcomplete or onnewscene for each scene