SWEET HOME 3D VIEWER v 4.3 ... Applet users may press the space bar to switch between aerial view and virtual visitor view, once they clicked in the applet.
Is there a way of switching between levels in the WebViewer?
I know I can upload two separate files saved with different level views, not really a problem. But before I do I just wanted to check whether I need two or more files. Just in case I missed a script argument or an actual command in the Viewer.
Virtual visitor, yes, but aerial view? Sorry, I am probably missing something here. Will contemplate in the morning and see if my question still makes sense.
ok
BTW - my challenge is in the three floor/level structure I sent you in a concept link: present the visitor with a plan overview of three different floors.
I didn't think it could be handy in that case. You should save your home with the 3D view > Display all levels menu item selected or with the last level selected.
One of my concern in introducing a level navigation system is that I fear it would be too complicate for the end user to use it in some situations. Keep in mind that the viewer targets generally a simple web user who doesn't know anything about Sweet Home 3D and its multi level system. He would probably understand easily how to go from one level to the other with a combo box, but as soon as he would change the elevation of the point of view himself, he could easily get lost.
With this in mind, I had a new idea about level management in the viewer, which would be cheaper to program: I could add parameters to the applet that would select a given level or a stored point of view. Thus, if you want to view the 2 levels of the same .sh3d file, you could show two viewers in the page that would use the same .sh3d file, avoiding to download a second .sh3d file.
An other idea would be let the web page programmer cite the keys he wants to associate to levels or stored points of view (for example, L could be associated to a point of view named "Living room"). I see two advantages for this solution: it's not difficult to program and would oblige the web developer to describe these associations himself in a quick guide of the page showing the viewer. What do you think?
If I understand, I think either solution would do the trick. Adding keys to move around would be easy to add to the web-page and would give "favourable" view-points. So, yes, I think that sounds like a good idea. ok
