[Plugin] Image 2 Model

sdmitch

Adam, Your image worked exactly like mine so I have attached Image 2 Model I. When you execute the plugin, The Open panel will allow you to select the source folder for the images. Next, the Save panel will allow you to select the destination folder for the models. An inputbox will let you choose whether the image is to be "stood up" and the width for the images. Since this is a "batch" process these options will be applied to all images in the source folder.

I still haven't resolved the problem of the saved file not being frontview and zoomed extents. It seems that it saves the model however the default template is setup.

Check it out and let me know how it worked for you.

batch process images into components that are saved in a model file

EarthMover

Works great with one exception. Can you perhaps set it to save just the newly created component and not save a copy of "Susan" along with each new .skp? Perhaps that's is the issue you are already referring to. I need to be able to compile these plants through the component folder. Other than that it's working like a charm!!

Also, just noticed that the component is still an "image". Possible to explode that down before the component conversion? Not sure if the final .skp files will work with all render engines with 'images' embedded.

sdmitch

If Susan is showing up it because she is in your default template.

I take a look at exploding.

TIG

You could always some code at the start to erase all model entities...
Sketchup.active_model.entities.erase_entities(Sketchup.active_model.entities.to_a)
[or a Sketchup.active_model.entities.clear [edit]]
Then .purge_unused for all model components, materials, layers and styles before adding the new image into the now sanitized model.
Surely image.explode will do the desired extra step ?

sdmitch

Added a .clear! to make sure the new file is empty. Exploded the image and hide the edges.

Image2Model.rb

TIG

The 'entities.clear' only erases the instance of Susan [and any other stuff placed in the default template].
BUT the definition still remains in the SKP, as do any now-unused related materials, layers etc.
It's best to have a '.purge_unused' for these after the '.clear'...