[Plugin] VisMap - Layer/Scene Visibility Map
-
'Layer0' is most often used as the current layer - you then put 'assembled' groups/components/etc on other layers to control visibility. However, you can set any layer as the 'active' one BUT it's not recommended without a good reason... An example would be you are puttings dimensions on the model and want them all to be on layer 'DIMS' - make that the active layer, add the dimensions [you can then switch them on and off separated from everything else] BUT remember to go back to active=Layer0 afterwards otherwise chaos will ensue...
-
@tig said:
'Layer0' is most often used as the current layer - you then put 'assembled' groups/components/etc on other layers to control visibility. However, you can set any layer as the 'active' one BUT it's not recommended without a good reason...
Ah yes I should have written ... "always going to have to be the active layer" when using VisMap
-
@chrisglasier said:
"always going to have to be the active layer" when using VisMap
Actually, Chris, I'd turn Layer0 off, if I could. In my tutorial I teach the common gospel re Layer0, but I don't believe it. I consider a model incomplete until Layer0 is empty.
-
@martinrinehart said:
@chrisglasier said:
"always going to have to be the active layer" when using VisMap
Actually, Chris, I'd turn Layer0 off, if I could. In my tutorial I teach the common gospel re Layer0, but I don't believe it. I consider a model incomplete until Layer0 is empty.
Yes I agree, empty, active and not an option in VisMap! Otherwise if you try and hide another layer that is active you will get an alert "You cannot hide an active layer" or something like that.
-
Sorted layer names.
These two are not in the .zip yet. Please rename "vismap.txt" to "vismap.js", try them in .../Plugins/Vismap and let me know.
Thanks.
-
@martinrinehart said:
Sorted layer names.
These two are not in the .zip yet. Please rename "vismap.txt" to "vismap.js", try them in .../Plugins/Vismap and let me know.
Thanks.
Just in case you want feedback here are two screenshots. Layer0 is empty, active and visible in all scenes. Some other layers also seem incorrectly checked - awkward to crosscheck though.
Perhaps the VIs strings did not get sorted (see top row, which was presumably previously level0).
And you really ought to address the awkwardness of the scene names and disappearing headers and unnecessary buttons (in my opinion,of course!).
Chris
-
Alphabetizing works great.
It still has a problem with pre-existing models with many layers and many scenes. I tried a new approach: I deleted all but one scene and re-saved the model with a different name. VisMap still would not load the layer names. (see attached)
Another request: Since you can have multiple models open at the same time, wouldn't it be a good idea to have the file name in the VisMap dialog box title?
![After clicking on "Get Data from Model"](/uploads/imported_attachments/M321_Screenshot2009-09-25at4.54.52PM.JPG "After clicking on "Get Data from Model"")
-
-
@chrisglasier said:
Perhaps the VIs strings did not get sorted (see top row, which was presumably previously level0).
Can you send me a model? Post here or MartinRinehart at gmail dot com.
@chrisglasier said:
And you really ought to address the awkwardness of the scene names and disappearing headers and unnecessary buttons (in my opinion,of course!).
Ground-up rebuild, but not anytime soon. Scene names should be in a separate window you can move/size to suit. Title should be in a frame you can fold away. Scene #s should be frozen. You should have Ctrl/+, Ctrl/- to adjust size....
-
-
@unknownuser said:
The Layers SU Window is small, redimensionable, fully interactive and has a table scrolling. Furthermore, it allows to add / remove layers and configure them dynamically. You will miss however the Sorting into alphabetical order! Fredo
Just for the sake of good order:
On a PC you can sort layers alphabetically by clicking on "Name."
Pedantically
Chris
-
Thanks to you guys, I've now reproduced the issue in a modest model. Probably closing in on the solution, though I won't be on it any longer, today.
-
@chrisglasier said:
Just for the sake of good order:
On a PC you can sort layers alphabetically by clicking on "Name."
Pedantically
Chris
Chris, You are right actually. You can also sort them by visible / invisible and by color.
We should sometime look at what the SU engineers are doing in the native application
Fredo
-
@chrisglasier said:
Please download sceneModel R1.4.zip from here.
Page not found
We're sorry, but we were unable to locate the page you requested.
-
@bob james said:
@chrisglasier said:
Please download sceneModel R1.4.zip from here.
A Google alert this morning Hong Kong time says it has recovered the page (I must have made some balls up with the new R1.05 plugin attachment), and it seems OK from here. I have also sent a copy of the zip as a reply to your email.
Thanks (and apologises).
Chris
PS Martin did you have the same problem?
-
Gentlemen:
This pair should be smarter about which boxes are initially checked.
-
it did not work for me on mac.
-
@martinrinehart said:
Bob, I need a sample model.
I took my main model (40MB) and started deleting layers (after I had deleted all but one scene). It initially had 205 layers and 22 scenes. After each set of deletions (about 20 at a time), I updated the scene and saved the model, then tried to "Get Data From Model". [VisMap dated 28 Sep 2009]
I finally had to delete ALL the layers except Layer(0) before VisMap would "Get Data from Model". (See Attached)The really weird thing is that the file is still 13.6MB!!!!!!(See Attached)
I can send you this if you can handle 14MB.This suggested something not right in how SU handles "something". How could a model with nothing in it be 13.6MB
![Shows the "empty" model is still 13.6MB](/uploads/imported_attachments/Qc7T_Screenshot2009-09-28at5.35.12PM.png "Shows the "empty" model is still 13.6MB")
-
@edson said:
it did not work for me on mac.
I tightened that up a lot. That's Ruby catching an error and forwarding it to the WebDialog to show to you. Your model has some sort of internal damage. Try "Purge Unused."
If that doesn't work, make a copy, delete half your layers and try again. If that fixes it, you've deleted a bad layer. If that doesn't work, make another copy and delete the other half of the layers. The remainder should work. Continue, working on quarters, eighths, ... until you find the bad layer.
If you can't isolate a single bad layer, try rebuilding one layer at a time: turn all but one layer off. Select all, copy to clipboard, open fresh model, make a recipient layer, paste from clipboard. Vismap it to be sure it's clean. Repeat.
Good luck.
-
@bob james said:
The really weird thing is that the file is still 13.6MB!
I assume you "Purge Unused"? I don't want a copy. Your model has issues.
Use the technique I suggested to Edson to rebuild. One layer at a time, select all, copy, paste into fresh file/fresh layer. Save. Keep Model Info open to File and watch size carefully. Use Vismap as an integrity check while you rebuild.
Good luck.
Advertisement