SKM files and the API

[medeek]

Currently with the Wall Plugin (that is in active development) I have a few hard coded materials that the user/designer can select from. Once the user chooses one of these materials I then create the material on the fly either by assigning a color or a texture:

Code: Select all

 @Lumberptmat_db = "#ffe5cc"
    @Lumberpt_mat = mats.add(mat_name)
    @Lumberpt_mat.color = @Lumberptmat_db


or something like this:

Code: Select all

 @Lsl_mat = mats.add(mat_name)
    @Lsl_mat.texture = File.join(this_dir,'materials/WOOD_OSB.jpg')
    @Lsl_mat.texture.size = [36.0, 4.0]

However, I would like to make it possible so that the user can create their own library of files (using .SKM files) and then just have the plugin load the applicable .SKM file into the model.

Somewhere I was reading that SKM files were creating issues for certain previous SU releases but this may be outdated information.

I'm just wondering if there are any known problems or issues with using SKM files and the API before I get too far down this road, that I should be aware of.

[TIG]

See http://ruby.sketchup.com/Sketchup/Mater ... nce_method
This method lets you load a SKM material directly into your model's materials - but it's only useful for versions >= v2017
If your toolset needs earlier version support... then, if the named material doesn't exist you will need to make a new material, and then add a texture to it, with scaling etc...

[medeek]

After a little further investigating I realized that it only works for 2017 and later. So basically this feature is fairly new.

I actually would like to make the switch to an SKM based system but with this feature being so new its stability concerns me. If it is running solid though I will probably switch.

[TIG]

It works fine in >= v2017...
Try it...

[medeek]

Most users of the plugin are SU 2018 but I've received some kickback from others so I may have to put this plan on hold and go a different direction.