Family Management Utils - WIP

UPDATE

This tool I've developed works on door and window families between different files letting the user edit them inside a single control file and pushing the edited families back to the other files. I've collected a few lines of code and put it all together with a very simple interface.

This is the workflow I've imagined:

1. Link the different projects into a single control file (CF)
2. Acquire the families from the linked files cliking on Copy Types
3. Delete duplicate types if necessary
4. Create assemblies with 3 main views and dimensions for each type, assigning a unique Type Mark automatically, each assembly is named with this syntax: (TypeMark)_Family_Type
5. Edit the components as necessary, fill in the data where needed and then update the linked files with the new version
6. You can finally create assemblies in each linked file for documentation purposes, each assembly is created in the first phase and demolished right in the next phase of the phase sequence, so to not interact with the actual project.

During the process the linked files have to be unloaded, keep in mind that also the family type names shouldn't change before the update, otherwise the tool won't be able to perfomr the update as expected.

For the sake of this example I'm using two linked files, a simple one and a workshared one.

In both cases there are the same door and window families and I'm showing the steps of the workflow, when the linked files are loaded the type mark for the family type in common between the CF and the links can't be changed, this is true for any other parameter such as width, height or material finish.

Once in the linked file a purge unused is recomended.

I still haven't figure out how to dismiss automatically the dialog when reloading families and override the parameters. Any suggestion is appreciated.

Auto Assembly Macro - WIP

In this video I'm showing the results of a macro I'm working on these days that allows to create an assembly for each door and window type present in the project.
It's still a work in progress though, but what it does is pretty clear:

1. create a generic wall sample to host a family instance of the door / window type
2. create the family instance
3. create an assembly with the family instance, its nested shared families and the hosting wall, whose category is after the family category and the name is a combination of the family name and the family type
4. increase the mark type and assign it to the family type
5. change the phase of creation and demolition of the assembly to be respectively the first and the second in the sequence
6. create three assembly views (plan, elevation and section)
7. create two major dimensions in the elevation view (I'm thinking of an early stage door/window schedule for this development)

There are still issues with curtain wall components though, need to fix that.

Using this method it's possible to create a source file that contains all the families and manage them with type marks, materials, and so on very effectively. Then the necessary editing can be extended to other project files really easily with the concept exposed in the previous post. Getting closer.