I created a clock family using nested components. The size of all components are:
Hours.rfa: 304kB
Minutes.rfa: 304kB
Seconds.rfa: 388kB
Hourplate.rfa: 328kB
Total filesize is a baffling 6,6MB!!!
Does anyone have an idea on how this happened? All components are used just once. All visibility constraints etc are located inside the components. So to me, it doesn't seem right that the file size is multiplied by 5.
Purging or save as doesn't seem to have any effect. Does anybody know what's going on here?
EDIT:
Ok, so I rebuild the entire family. Thought it might have something to do with redundant data floating around somewhere. But that doesn't help a bit. Filesize is somewhat smaller (6.2MB) but it still doesn't account for the difference in file size. Could nesting parameters have something to do with this?
Hours.rfa: 304kB
Minutes.rfa: 304kB
Seconds.rfa: 388kB
Hourplate.rfa: 328kB
Total filesize is a baffling 6,6MB!!!
Does anyone have an idea on how this happened? All components are used just once. All visibility constraints etc are located inside the components. So to me, it doesn't seem right that the file size is multiplied by 5.
Purging or save as doesn't seem to have any effect. Does anybody know what's going on here?
EDIT:
Ok, so I rebuild the entire family. Thought it might have something to do with redundant data floating around somewhere. But that doesn't help a bit. Filesize is somewhat smaller (6.2MB) but it still doesn't account for the difference in file size. Could nesting parameters have something to do with this?
Comment