related sketch

[MassiVonWeizen]

make a pack&go excluding the details that must be shared

 

[genesis1975]

I didn't understand your answer to No.14.

 

[genesis1975]

and if I brutally make paste copy of wins of the whole folder?

 

[genesis1975]

as I told you I did copy with pack and go only of a part, not belonging to any set, and I put it in another folder...so doing the copy I made did not keep the original references, as you said, but changed them.. .

 

[drake]

It is good that the elements that can be used in different works are part of a library. then these parts can be enriched with all the configurations you want. you must have clear ideas about how to manage your archive. said this, even when I leave from a job done and I have everything inside the same folder I make the paste copy of win, it works perfectly. if you have external components, it is good to use the pack with the necessary precautions, choosing the components to be copied and those that instead have to stay where they are, as a bookcase. certain is that components of a library should be placed in an external folder at any work

 

[MassiVonWeizen]

I didn't understand your answer to No.14.

What is not clear?
the funzine system in this way:
the pack&go makes a copy of the selected file, together or part, including all references in it.
if it is a set will copy all parts, drawings (if selected) and any assemblies with shared references (but not the parts contained in these possible assemblies)
if you draw a part you will copy the drawings (if selected) and any references to other parts or assemblies (in this last case you will copy only the aasieme and possible share)
from the list that appears in the pack&go you can exclude files to be copied simply by removing the check; at the opening of the copy made the items excluded from the list will remain the original ones.

I did copy with pack and go only of one part,not belonging to any group, and I put it in another folder... doing the copy I made did not retain original references, as you said, but changed them.. .

of course because there are no references to maintain. this because, as mentioned above, the pack&go does not include a set in which it is contained unless it has shared references (if for example relationships a sketch of the part to a plan of the assieme then sharing is there and the assieme will be copied because otherwise the sketch would give error). my explanation of post #14 always does faith in the context, subtent in this case, of the part with shared references since it is on this that the discussion is about.

and if I brutally make paste copy of wins of the whole folder?

you are with a copy in which you will have to remand references and files.
If I were you, I'd start making a file with all the questions and answers you ask so you can collect ideas and have your information under your eyes.


looking for a pattern I had posted I found a similar request to one that you did the last day on the origins of files