CAD would do this when opening a file with references.ġ) Is that filename already loaded in memory? ( I can accept this one is mandatory for reasons that are over my head)Ģ) Is the file in the EXACT PATH stored in the parent file I'm opening?ģ) Display dialog, "Referenced file path does not exist, please fix your $#!+."ĭone, that's it. If I could choose (thank goodness I cannot) it would be a 3 step process. What I don't understand is why using the path that is stored in the parent file is so far down the list. Solid Edge has a goofy way of looking for files as well, feels kinda like how SW does it. I prefer a step of 1."This is the file that should be here." rather than "Well this is the file that is supposed to be here but it does not appear to be here so let me run all over this disaster of a file structure you have here pretending I know how it works even though you don't know how it works so I can decide which one I think is supposed to be here" Yes it's not random.just a really bad idea on how to decide what files should be in an your assembly.
0 Comments
Leave a Reply. |