I am in the process of building my Smart Door & Window library and I have a few questions.
1. Looking at the .dor files that come with Datacad it looks like they can use a base path for the symbol locations. Are these using the Symbol base path? I like the idea of using a base path but not sure it would work well with our current setup for our existing symbols since it would be looking for the next part of the path at the root of our existing symbol library which it's management rules would not jive with having a library of entities tossed in the root. Think I want to keep our Smart Entity libraries on our local drives under the support files like our hatch patterns and linetypes. I am thinking about putting the 2D/3D symbols used for the Smart Entities in the same folder as the .dor/.win files Just from a file management standpoint I think I just like having the corresponding files next to each other since I'm going to have one .dsf for each .dor file. I think if I could use the Smart Entity Base Path instead as the root for the smart entity symbols that would work perfectly. Any reasons why this might not be a good idea? Anyone else doing something completely different/better?
2. Am I right in thinking the only way to get the multiple color options for 3D door symbols is to create a collection of door symbols with materials for each color option? Or is there is batter way to handle this with a single set of door types replacing the materials in the drawing? I was thinking of doing something like below.
Example: Door Types\Andersen\Frenchwood\Gliding\Exterior Color\Interior Color\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\White\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\Pine\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\Maple\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\Oak\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\Sandtone\Pine\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\Sandtone\Maple\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\Sandtone\Oak\FWG6080.dsf, FWG6080.dor
Looking at this task, it sure would sure be nice if we had a way to replace materials within symbols at the drawing level or a way to view the symbols information (is it a table or database?) that we could swap out info.
3. Another way to help simplify the material options would be a material override/highlight that would ignore the symbols materials, and use the one defined in the manager. Would also want a per entity override in the Door & Window Properties dialog, because why not have more awesome?
Thanks for any ideas or direction!
1. Looking at the .dor files that come with Datacad it looks like they can use a base path for the symbol locations. Are these using the Symbol base path? I like the idea of using a base path but not sure it would work well with our current setup for our existing symbols since it would be looking for the next part of the path at the root of our existing symbol library which it's management rules would not jive with having a library of entities tossed in the root. Think I want to keep our Smart Entity libraries on our local drives under the support files like our hatch patterns and linetypes. I am thinking about putting the 2D/3D symbols used for the Smart Entities in the same folder as the .dor/.win files Just from a file management standpoint I think I just like having the corresponding files next to each other since I'm going to have one .dsf for each .dor file. I think if I could use the Smart Entity Base Path instead as the root for the smart entity symbols that would work perfectly. Any reasons why this might not be a good idea? Anyone else doing something completely different/better?
2. Am I right in thinking the only way to get the multiple color options for 3D door symbols is to create a collection of door symbols with materials for each color option? Or is there is batter way to handle this with a single set of door types replacing the materials in the drawing? I was thinking of doing something like below.
Example: Door Types\Andersen\Frenchwood\Gliding\Exterior Color\Interior Color\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\White\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\Pine\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\Maple\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\White\Oak\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\Sandtone\Pine\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\Sandtone\Maple\FWG6080.dsf, FWG6080.dor
Door Types\Andersen\Frenchwood\Gliding\Sandtone\Oak\FWG6080.dsf, FWG6080.dor
Looking at this task, it sure would sure be nice if we had a way to replace materials within symbols at the drawing level or a way to view the symbols information (is it a table or database?) that we could swap out info.
3. Another way to help simplify the material options would be a material override/highlight that would ignore the symbols materials, and use the one defined in the manager. Would also want a per entity override in the Door & Window Properties dialog, because why not have more awesome?
Thanks for any ideas or direction!
Thanks! - Josh
Do. Or do not. There is no try.
Josh's Digital Downloads is come back online soon. Stay tuned. (soon is a relative term)
Do. Or do not. There is no try.
Josh's Digital Downloads is come back online soon. Stay tuned. (soon is a relative term)