@Stefan Videnov wrote:
Even if it's implemented not exactly 'in place', but it is in the same file (different window?) it is still going to be many times easier to coordinate than the separate file system that we have now.
Most of us agree with this long-standing wish. But, I just want to make sure you realize that modules do NOT have to come from a separate file. Self-linking has always been possible and the easiest way to handle some situations. Further, self-linked modules never have issues with Attribute coordination, the biggest problem with external hotlinks.
Some self-linking hotlinks can be handled without any special view settings. For example, a structure where certain floors/stories are clones of another story can simply hotlink the desired story onto the target story.
Other module content that is placed randomly throughout the project but which should be identical in all places - can be placed on its own story. Many of us create these as negative stories - below the foundation, and then change the view settings for all sections / elevations / 3D to ignore these hidden stories. Then you can edit the module on that special sub-story and the hotlinks to it will update throughout the project. In choosing to use this approach, it makes sense that the module is reasonably unique to the current project. Modules that you would re-use across lots of projects probably are best placed in their own files.
Finally, do not forget Publisher, which can publish MOD files from a project. Thus, you can have modules in sub-stories that are linked into the current project directly... but for which a Publisher set will also generate MOD files to be used in other projects...for as many modules as you create in the file.
Placed-module update is not automatic with self-linked hotlinks, so you still need to go to Hotlink Module Manager after changing your sub-story content and click Update to update all placed instances... or right-click a placed module and click Hotlink Module > Update Module and all related Hotlinks as seen in this screenshot:
PS One more caveat besides manual update (or auto-update on re-opening the file): the self-hotlink does not come from the live/open file, but from the last version saved on disk (or published by TW). So, if you make changes to a self-linked module on negative story... you must save the PLN before doing the Update Module. 👍
Stefan asked me in a PM to explain our method a bit more, rather than keep it in PM, I figured it might be interesting for more people.
Quick screen shot of the 'workplace'. On the top left of the navigator, you can see our saved view (MOD Module Werkplaats). After opening that, you scroll / zoom to the module you want to change, in this case 'PLG_A' (shorthand for floorplan A). We select the elements and then 'unpin' them on the top right, so they are no longer linked to the custom renovation filter.
Next, make your changes, you can use trace and reference to see the module in relation to the model. When you're done making changes, selec the elements again and then save (and overwrite) the module file. After that, 'pin' the elements back to the filter, update modules and you are done.
Perks:
- no need to manage attributes across files
- easy to copy around elements between multiple modules
- easy to edit module in relation to the model
Still looking?
