Great! It definitely took me a while and some experimentation to grasp it. Even what I share here is a slight simplification of what's actually happening, but for all practical purposes, thinking of it this way has worked for me.
I really like that merging explaination. I have been using onshape for a couple years and don't really merge because of the unpredictable feeling it gives me. And because it always seems like one workspace somehow isn't up to the same library version as the other and I have contact support to update it.
Yep! It can definitely feel intimidating, but its really powerful too which is why I went to all of the trouble to make sure I knew how to predict the merge behavior. I tend to prefer keeping my branches very single-purpose, and merging them back to a Main workspace as soon as I can. That cuts down on the library version mismatch issues (which are really more of an inconvenience more than an issue). I try to avoid making a branch, and just working on all kinds of things there till it just kind of becomes the defacto Main workspace.
@@ovyl I usually have one extra branch that I use for drawings. I configure everything like crazy and like having the branch as a sort of storage space which also forces the drawings to be using a version or revision of the item. Anytime I branched for design purposes, the branch either was completely discarded and rejected or just became the new main workspace
I'm having trouble with that part, I created it for "Student B" (me) and I can't do it the same way for "Student A" (my partner), I don't know how to do it again from scratch, I would appreciate your help...
Hmm I'm not sure I follow the issue, but this kind of topic is probably better for the Onshape Forum anyway. There's an educator section: forum.onshape.com/categories/education-community
Nice job Evan! Interesting way of explaining merging as stacking the merged on top. I had not realized that it keeps things in order like that. Would be good to see how you think about and resolve conflicts. I use version and branches all the time, more for the risky trial only type things. Not really deep diving into team use and other ways to use power of branch/version.
Thanks! Do you have an example of a conflict you may have run into? I think if everyone just keeps each branch contained to just one general idea at a time there's usually not much issue.
Why Can't we Edit Versions? What's the point of it Saving if We are Locked out of Design Changes. I feel Now I will Just end up So many Versions and All for Nothing. I appreciate all you Work by the way. Thank You. Im New Here from Solidworks.
Coming from Solidworks I was a compulsive "ctrl-s" person. It takes a mindset shift, but it's a great system. You don't need to version in order to "save"-The work is always saved. Think of a version as a bookmark to help you find a point in the history. The immutability of it is one of the features. Yes you can end up with lots of versions, and hopefully there's a way to tidy that better in the future, but it's really not a big deal. They cost you nothing but a little clutter. You could re-name the irrelevant ones to something easy to understand to make the important ones stand out more.
Thanks! I suppose I didn't actually show which clicks are needed to merge, but fortunately it's the easy part to learn and it's covered thoroughly in the help documentation: cad.onshape.com/help/Content/merge.htm?Highlight=merge
Great explanation Evan. Thanks for sharing
My pleasure!
Fantastic explanation Evan, thank you!
Glad it helped!
Great video, Evan + Fractal Team!
Thanks, Charles
Thank you so much and the video is really helpfull to understand the branching and merging usage 👍
Great! It definitely took me a while and some experimentation to grasp it. Even what I share here is a slight simplification of what's actually happening, but for all practical purposes, thinking of it this way has worked for me.
I really like that merging explaination. I have been using onshape for a couple years and don't really merge because of the unpredictable feeling it gives me. And because it always seems like one workspace somehow isn't up to the same library version as the other and I have contact support to update it.
Yep! It can definitely feel intimidating, but its really powerful too which is why I went to all of the trouble to make sure I knew how to predict the merge behavior. I tend to prefer keeping my branches very single-purpose, and merging them back to a Main workspace as soon as I can. That cuts down on the library version mismatch issues (which are really more of an inconvenience more than an issue). I try to avoid making a branch, and just working on all kinds of things there till it just kind of becomes the defacto Main workspace.
@@ovyl I usually have one extra branch that I use for drawings. I configure everything like crazy and like having the branch as a sort of storage space which also forces the drawings to be using a version or revision of the item. Anytime I branched for design purposes, the branch either was completely discarded and rejected or just became the new main workspace
I'm having trouble with that part, I created it for "Student B" (me) and I can't do it the same way for "Student A" (my partner), I don't know how to do it again from scratch, I would appreciate your help...
Hmm I'm not sure I follow the issue, but this kind of topic is probably better for the Onshape Forum anyway. There's an educator section: forum.onshape.com/categories/education-community
Nice job Evan! Interesting way of explaining merging as stacking the merged on top. I had not realized that it keeps things in order like that. Would be good to see how you think about and resolve conflicts. I use version and branches all the time, more for the risky trial only type things. Not really deep diving into team use and other ways to use power of branch/version.
Thanks! Do you have an example of a conflict you may have run into? I think if everyone just keeps each branch contained to just one general idea at a time there's usually not much issue.
Why Can't we Edit Versions? What's the point of it Saving if We are Locked out of Design Changes. I feel Now I will Just end up So many Versions and All for Nothing. I appreciate all you Work by the way. Thank You. Im New Here from Solidworks.
Coming from Solidworks I was a compulsive "ctrl-s" person. It takes a mindset shift, but it's a great system. You don't need to version in order to "save"-The work is always saved. Think of a version as a bookmark to help you find a point in the history. The immutability of it is one of the features. Yes you can end up with lots of versions, and hopefully there's a way to tidy that better in the future, but it's really not a big deal. They cost you nothing but a little clutter. You could re-name the irrelevant ones to something easy to understand to make the important ones stand out more.
A lot of useful information but you didn't actually ever show a merge.
Thanks! I suppose I didn't actually show which clicks are needed to merge, but fortunately it's the easy part to learn and it's covered thoroughly in the help documentation: cad.onshape.com/help/Content/merge.htm?Highlight=merge