I am in need of a new type of object that I am calling a Module (working title).
Basically, it is like a group and a symbol had a useful baby.
I am working on a hotel project, and there are many repeated room types. I would like them to be symbols, but this comes with some serious downsides:
-Doors and windows can not be scheduled correctly.
-Walls can not join the walls in the symbol.
-Slight variations can not be made without breaking the symbol.
Obviously, if I make them all groups then every change to 1 has to be made to all.
It would be great if there could be this hybrid of a group and symbol.
The way I think this could work is that you have the base module that is then deployed like a symbol - except that its contents can interact with outside objects and can be scheduled and annotated separately. If you then make a change to the base module - the changes would then be pushed out to all the modules in the document. If a module had a unique element - any changes affecting that element would not be pushed to that particular module, but all other changes would.
This is coming up because of this hotel, but I think it could find many other useful functions as well.
If anybody has any suggestions on how to handle this workflow now - I would love to hear it.
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
Tom Klaber
I am in need of a new type of object that I am calling a Module (working title).
Basically, it is like a group and a symbol had a useful baby.
I am working on a hotel project, and there are many repeated room types. I would like them to be symbols, but this comes with some serious downsides:
-Doors and windows can not be scheduled correctly.
-Walls can not join the walls in the symbol.
-Slight variations can not be made without breaking the symbol.
Obviously, if I make them all groups then every change to 1 has to be made to all.
It would be great if there could be this hybrid of a group and symbol.
The way I think this could work is that you have the base module that is then deployed like a symbol - except that its contents can interact with outside objects and can be scheduled and annotated separately. If you then make a change to the base module - the changes would then be pushed out to all the modules in the document. If a module had a unique element - any changes affecting that element would not be pushed to that particular module, but all other changes would.
This is coming up because of this hotel, but I think it could find many other useful functions as well.
If anybody has any suggestions on how to handle this workflow now - I would love to hear it.
Thanks!
Link to comment
3 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.