Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

Can a Part be moved to another Part Studio?

johan_van_ravenhorstjohan_van_ravenhorst Member Posts: 19 ✭✭✭
edited March 2017 in Community Support
Extended version of the question:

Can a Part instance be cut/copy-pasted from the Part Studio instance where it was created to another Part Studio instance, including the corresponding feature tree items?

Assume that the other (receiving) Part Studio instance already contains a populated feature tree that needs to be preserved*. Note: The "Derived part" function does not copy/move the feature tree**.

Example usage**
Suppose that multiple parts have been created in individual Part Studios and that these parts have many (dimensional) inter-dependencies. In an assembly, these dependencies can be realized by in-context editing, or, alternatively, the user simply adjust each Part Studio manually which can be error-prone. Now if the parts need no relative movement, then a Part Studio may be a simpler option because dependencies can be realized without (switching) contexts. This insight may emerge only after already creating a substantial feature tree for each Part Studio. Recreating these features in the "part combining" Part Studio would cost additional time. Instead, moving parts including their tree would avoid that.

*  Added after Konstantin Shiriazdanov's reply.
** Added after 3Dcad's reply.

Best Answer

Answers

  • konstantin_shiriazdanovkonstantin_shiriazdanov Member Posts: 1,221 ✭✭✭✭✭
    the geometry of a part can be copied to another part studio using "derive" instrument, but feature history of a part will not be included, and actually it will be another part just with the same geometry. one may copy the whole part studio if the feature tree is needed
  • johan_van_ravenhorstjohan_van_ravenhorst Member Posts: 19 ✭✭✭
    edited March 2017
    @konstantin_shiriazdanov and @3dcad:
    Thanks for your fast comments, I adjusted the question based on these comments.
    The copy sketch can save quite some time, thanks for pointing that out.
  • konstantin_shiriazdanovkonstantin_shiriazdanov Member Posts: 1,221 ✭✭✭✭✭
    edited March 2017
    in os we actually have the ability to view the code of part studio, but we cant copy it and paste into the new part-studio.
    really would be interesting to know what OS team think about ability to "merge" two part-studios into a new one
  • leon_pootleon_poot Member, Developers Posts: 87 ✭✭✭
    in os we actually have the ability to view the code of part studio, but we cant copy it and paste into the new part-studio.
    really would be interesting to know what OS team think about ability to "merge" two part-studios into a new one
    Agreed, would be quite useful. Like you can merge different versions of a document, all new features are just added then... 
    You can merge one or several contexts (i.e. Part Studio build() functions) with FeatureScript, but that of course doesn't give you the actual tree features from those Part Studios, that's just the same as Derived.
    "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams, Mostly Harmless
  • Jason_SJason_S Moderator, Onshape Employees, Developers Posts: 210
    johan_van_ravenhorst,

    You could duplicate the Part Studio tab, right click on the duplicate tab ,and select Move to document. You'll have bring along the entire Part Studio, but you'll have the feature tree intact. 

    Note: The moved instance will no longer be tied to the seed Part Studio, so any updates to the seed will not be reflected in the moved instance. 

    I suggest using Derived to keep everything linked together, despite your desire to move the tree. 
    Support & QA
  • johan_van_ravenhorstjohan_van_ravenhorst Member Posts: 19 ✭✭✭
    edited March 2017
    @Jason_S: Your comment addresses moving a Part Studio to another Document, instead of moving a Part to another Part Studio. Or did I miss something?
  • Jason_SJason_S Moderator, Onshape Employees, Developers Posts: 210
    Yes, to another document. Sorry I did not make that clear. I thought you were looking to move a part to another Part Studio in another document.
    Support & QA
  • johan_van_ravenhorstjohan_van_ravenhorst Member Posts: 19 ✭✭✭
    @Jason_S: No problem. In the problem addressed here, the target Part Studio can be located in any Document, including the Document containing the source Part Studio.
Sign In or Register to comment.