D_Driver
2006-12-29, 04:37 AM
I understand the difference between a material key and a material tag essentially to be this:
Material tags are inherently more useful because we can create tags to most of the aspects of the material parameters available on the material ID properties page (unfortunately except KEY)
Material Keys are intended to be used in conjunction with the keynote text file which..well we will stop this sentence there.
What I found interesting is that if I desire to assign a keynote manually into the material definition (such as PT-1 for material Paint 1) I can do this, AND the material keynote does not really care that this value is not in the keynote text file.
I just tested this on a wall type that had not been keynoted and is true of the element type keynote also.
my question is: is there any danger in doing this? Programatically will this keynote symbol be looking to the text file at any time in the near future and finding this entry lacking give up the ghost?
thanks
Material tags are inherently more useful because we can create tags to most of the aspects of the material parameters available on the material ID properties page (unfortunately except KEY)
Material Keys are intended to be used in conjunction with the keynote text file which..well we will stop this sentence there.
What I found interesting is that if I desire to assign a keynote manually into the material definition (such as PT-1 for material Paint 1) I can do this, AND the material keynote does not really care that this value is not in the keynote text file.
I just tested this on a wall type that had not been keynoted and is true of the element type keynote also.
my question is: is there any danger in doing this? Programatically will this keynote symbol be looking to the text file at any time in the near future and finding this entry lacking give up the ghost?
thanks