E-Key
2005-11-17, 11:04 PM
There are two cases of conflict between family loaded into a project and the same family on the disk.
1. When the family is opening for editing from the project on Save command. Revit remembers the file path and asks for replacing an existing file.
2. When we load the family file from the disk. Revit asks about overwriting an existing version of loaded family in the project.
There is one problem to make a decision about overwriting loaded family or file on disk - sometimes I can't remember which version of the family is newer!?
So my wish is to store in the project not only family file path (thanks to Revit version 8!) but also the time when the family was loaded into the project. When we save the family during editing or load it into the project it will be fine to get the date and time information about conflicting families in the project and on disk.
It will make the choice easier and could prevent overwriting the family with older one's version.
PS. The date of of loaded family could be defined:
1. When load the family from the disk it's a date of the file
2. During the family edit session if there weren't changes in session after Save it's the time of last Save command
3. During the family edit session if some changes have done without family saving it's the time of last loading.
1. When the family is opening for editing from the project on Save command. Revit remembers the file path and asks for replacing an existing file.
2. When we load the family file from the disk. Revit asks about overwriting an existing version of loaded family in the project.
There is one problem to make a decision about overwriting loaded family or file on disk - sometimes I can't remember which version of the family is newer!?
So my wish is to store in the project not only family file path (thanks to Revit version 8!) but also the time when the family was loaded into the project. When we save the family during editing or load it into the project it will be fine to get the date and time information about conflicting families in the project and on disk.
It will make the choice easier and could prevent overwriting the family with older one's version.
PS. The date of of loaded family could be defined:
1. When load the family from the disk it's a date of the file
2. During the family edit session if there weren't changes in session after Save it's the time of last Save command
3. During the family edit session if some changes have done without family saving it's the time of last loading.