[Plugin] VisMap - Layer/Scene Visibility Map

MartinRinehart

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.

vismap.txt

vismap.rb

chrisglasier

@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.
vismap1 230909.png
vismap2 230909.png

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

Bob James

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"")

MartinRinehart

@bob james said:

Alphabetizing works great.

It still has a problem with ...

Bob, I need a sample model.

@bob james said:

Since you can have multiple models open at the same time

I also need a Mac. Will look at the name thing.

MartinRinehart

@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....

chrisglasier

@martinrinehart said:

Can you send me a model?

Please download sceneModel R1.4.zip from here.

chrisglasier

@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

MartinRinehart

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.

fredo6

@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

Bob James

@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.

chrisglasier

@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?

MartinRinehart

Gentlemen:

This pair should be smarter about which boxes are initially checked.

Ruby

Rename to "vismap.js"

Edson

it did not work for me on mac.

Bob James

@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

VisMap after all the layers were removed.

![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")

MartinRinehart

@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.

MartinRinehart

@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.

Edson

martin,
purge unused did not help. then i tried (sort of) your technique but by copying groups of five layers at a time to a new file and running vismap after each copy. it worked every time until all the layers had been copied.

EDIT: however, the error reported above is happening with every file i open. i do not believe every one of them have problems. purge unused does not help, fix problems returns no problems. i cannot imagine having to move all layers to new files for every model i work on. my conclusion: vismap is still not being able to handle big files with many layers and scenes.

MartinRinehart

@edson said:

it worked every time until all the layers had been copied.

EDIT: however, the error reported above is happening with every file i open.

I'm not certain whether this is a size or a Mac issue. This morning I've been making a movie promoting a club I've designed. Could you try it? If your problem reappears, we'll know it's platform-related.

Try http://www.MartinRinehart.com/download.html

The last of the four downloads, rf.zip, contains "club.skp". Open it, add a couple scenes and VisMap it. (This was my first SketchUp model, so don't judge it too harshly, please.)

Edson

martin,

i created some scenes and tried it with your file. it worked. your file has 3.8 Mb, mine have all more than 30Mb.

MartinRinehart

@edson said:

i created some scenes and tried it with your file. it worked. your file has 3.8 Mb, mine have all more than 30Mb.

Thanks!

I am not understanding this. The VisMap Ruby code is getting an error. It collects an array of layer names, an array of scene names and a string with one "V" or "I" for each scene/layer intersection. That is a very small amount of data, even for your 30MB+ models. Hmmmm.


# /models/rubies/t.rb

require 'sketchup'

model = Sketchup.active_model
layers = model.layers
scenes = model.pages

puts
puts 'This model has ' + (layers.length).to_s + ' layers and ' + (scenes.count).to_s + ' scenes.'
i = 0
scenes.each do |s|
	puts
	puts
	puts 'Processing scene ' + (s.name).to_s
	if s.layers.length > 0
		puts 'Invisible layers in ' + (s.name).to_s + ' are;'
		s.layers.each do |l|
			print l.name + ', '
		end
	else
		puts (s.name).to_s + ' has no invisible layers.'
	end
	puts
end

Above is a little reporter that lists each scene in a model and the layers within that scene that are invisible. Try it on my small model to make sure it works. Select All here, copy to clipboard, paste into editor, save to any convenient directory as "t.rb". With small model open in SU, open the Ruby Console window. In the white input line enter:

load '/where/you/chose/t.rb'

and press Enter. You should get a report. (Expand the Ruby Console a lot to view it.)

Assuming that works, load one of your models into SU. In Ruby Console, up arrow, then Enter. That will start the report on your model. (Good time here to get a fresh cup of coffee.) It will run successfully, to completion of your last scene, or it will crash. I want it to crash, and I want to see the error message.

If runs to completion, please ZIP up and send me a copy of enough of one of your models to reliably refuse to VisMap. MartinRinehart at gmail dot com. And thanks again.