Hi guys, we are working with large files and lots of xrefs (in lack of a Rhino word: xref is externally referenced files)
But we have a problem when we reference in a files that also have same files referenced in…
Here is a better example:
File A is first half of a project
File B is second half of a project (A and B are two physical projects handled after each other, with different plans, sections etc. and different project names and numbers are should not be handled as one Rhino file. It’s just how it is in real world)
File C contains the landscape around A and B
File D contains the 3D scan of the site
Both File A and File B needs C and D referenced in.
But then I need File A referenced in to File B so I can see the whole project together, but since they both have C and D referenced stuff gets odd.
AND to make it worse, if I save A with B referenced in, and THEN open B and want A referenced in… then I get a loop, since A allready has B in… you get the picture?
How could Rhino handle cross references like this better when worksessions are NOT an option?
Ideally it would read the file, say: "Oh, I allready have that file referenced in, so I ignore it, and then continue like nothing odd had happened.