Maybe there is another way to do that, but this worked fine for me:
First you have to define a custom attribute to store the material, something like:
myMatCA = attributes _mat
attribID:#(0x3b86c5cc, 0x336784d7)
(
parameters main rollout:params
(
_material type: #material ui:btn_material
)
rollout params "pick Material" width:162 height:258
(
materialButton btn_material "Pick Material" pos: width:119 height:25 material:undefined
on btn_material picked newMat do
(
btn_material.caption = newMat.name
)
)
fn getRollout = params
)
the attribID can be generated with the genClassID() function.
Then, you can add a new node:
newTrackViewNode "yourCustomName"
This will just add a new track (you can check that on the trackview), named "yourCustomName" that will serve as a container for your custom attribute. You should then add the custom attribute to that node:
mCA = myMatCA
custAttributes.add (trackviewnodes ) mca
Now everything is set up to start writing your code. To read or set the material, use
trackviewnodes._mat._material
and if you need an interface for your scripts, you can get the rollout with
trackviewnodes._mat.getRollout()
This is a very simple and basic setup, from there you can play around, like creating multiple material properties (or any other kind of properties) for your custom attributes, or adding multiple tracks to store different materials, or maybe keep just one global track, and add different controllers with the custom attribute on each one, etc. There are multiple possibilities from there.
I hope it helps,
