Maybe this has been wished for or discussed before.
I had this sudden thought about how you could have a very long list of classes to cover all sorts of objects in a single file.
How about being able to set (or bind) specific classes to specific layers? So depending on a layer that is set only classes that are universal to all layers and those classes that are set(or bound) to the layer would show up in the list. This may be an interesting way of reducing the visible list and managing those classes more tightly.
An example that I have in my work flow is a class called "Roof" and in it I have sub classes like Roof Main, Soffits, Gutters, Fascia and others related specifically to roofs. These classes could only show up on the classes list when I'm currently working in the particular roof layer. I always separate my roofs from the other parts of the model. By extension I would not see classes that are unrelated such as Walls. (Though walls could in many ways be apart of roofs but I'm using this class as an example in a basic way).
Any thoughts out there on pros and cons on this idea? Is there any value in this other than what I've mentioned above?
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Markvl
Maybe this has been wished for or discussed before.
I had this sudden thought about how you could have a very long list of classes to cover all sorts of objects in a single file.
How about being able to set (or bind) specific classes to specific layers? So depending on a layer that is set only classes that are universal to all layers and those classes that are set(or bound) to the layer would show up in the list. This may be an interesting way of reducing the visible list and managing those classes more tightly.
An example that I have in my work flow is a class called "Roof" and in it I have sub classes like Roof Main, Soffits, Gutters, Fascia and others related specifically to roofs. These classes could only show up on the classes list when I'm currently working in the particular roof layer. I always separate my roofs from the other parts of the model. By extension I would not see classes that are unrelated such as Walls. (Though walls could in many ways be apart of roofs but I'm using this class as an example in a basic way).
Any thoughts out there on pros and cons on this idea? Is there any value in this other than what I've mentioned above?
Cheers,
Mark
Link to comment
7 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.