Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- 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.
Answers
Any feature that touches the ghost image (sketch relations/faces/transforms/etc...) will be linked to that touched entity. Whether or not that menu is on none or whatever.
In-context is not a configuration. Just a reference to an assembly
HWM-Water Ltd
Should the context be active if the selected context is "none"?
I don't understand why I see the edit (the boolean operation) when I haven't selected a context.
I can understand that I see the boolean operation when the proper context has been selected, but if I always see it, then a context wouldn't be necessary;)
I probably just clicked something I shouldn't have.
if you do see additional parts in your studio, chances are you selected them while doing a "Transform->copy in place"
The cabinet is cut (boolean operation performed) when no context is selected, as shown in the screenshot.
The only difference when I select a context, is that I see the ghost, but the cut is still there even if "none" context is selected;)
I don't expect the in-context edit to affect all my future cabinets.
If I create a new assembly now and insert a simple cabinet, it has a boolean operation done to it.
I'm just totally not getting it right now;)
For example here, I create an in-context edit on the same cabinet, but to each different instance (there are 5 cabinets here, so I have a different context for each, cause they are cut in different ways)
But no worries, we can fix this.
Create a new configuration (one for each in-context reference) I would assume a "list" configuration type would do here.
Name each configuration similar to the names of your In-Context reference (to make it easier to find later)
Then suppress the feature on the tree in all configurations except the one you label.
Make sure you create a config in that list called default. which would have all features that use in-context suppressed.
Does that make sense?
In-context is not configuration. It is just a reference to an assembly as THAT one part remembers it. Not to be confused with "this instance of the part, in the assembly".
Maybe a short story will help spur the imagination...
I can imagine a "part studio" like a Buddhist monk sitting in meditation.
He knows all of his disciples (Parts), He knows every cut and bruise they ever got (extrude/move face...)
One day someone asked him, "I saw Jim in the garden, It was 1:23 pm, Kevin was 10" away, They were shaking hands, Can you join them together where they touch?"
The monk pictures the scene in his head and remembers it forever (In-Context reference created)
The monk says "Yes", then the two men are now connected by their flesh like Siamese twins. (Boolean Union 1)
The monk now closes his eyes and goes back to meditation (in-context set to None)
The two men are still connected by flesh, even though the monk is no longer thinking of them.
A week later, the two men approach the monk and ask if he can connect their other hands in the same way. (I don't know, these guys are weird like that..)
The monk looks at them, and says "Let me remember..." (switches back to in-context mode) "Let's see, It was in the garden at 1:23 pm, You were standing there, He was 10 inches from you, you were shaking hands, but you were only shaking hands with your right arms.. Sorry, I cannot join your other hands, as they are not touching."
The two men run off to the garden and stand in the same spot, this time they hold both hands and call out to the monk. "How about now?" (Update context)
The monk opens his eyes, "I see a garden, it is 5:23 pm, Kevin is now 11" away from Jim, they are holding both hands" The monk thinks about it and joins their other hands (boolean union 2), then he closes his eyes and goes back to meditate (in-context None).
Out of nowhere a portal opens up from the wall, two men step out with both hands connected, They are from the 18th dimension.
The monk recognizes them as Jim and Kevin and asks "What is the problem?"
"We were minding our own business in the kitchen, when out of the blue both of our hands were joined!"
Being a kind and ominpresent monk, he opens his mind to the multiverse (configurations) he then sees dimension 18... He points to it and says "You, and only you may walk a separate path" (Suppress Boolean Union 1 & 2) and like that the two men's hands were free. They quickly wave to the two men in the corner with both of their hands still connected (they are from 'dimension 2' (config 2) and did not ask to be separated), then like a flash they leave back through the portal from whence they came (change part studio configuration back to default)
I think that about sums up every situation of in-context / configuration relationships. If I'm confusing you further let me know. I can ramble a lot sometimes.
Until one day, the serpent came upon a Demon.
The Demon cursed the serpent, driving him insane, causing him to eat his own tail.
The serpent was blind.
But there were those who could see, who knew the serpent's true path. So they created a weapon to destroy the Demon.
They hid the weapon in the snake's den, where he waited for his madness to end.
But it never did. For the seers discovered that the only one who could wield the weapon was the Demon itself.
And so the serpent was doomed to wait in madness...forever.
I like yours better
https://www.youtube.com/watch?v=AzQ16zXdtqg
https://vimeo.com/228643062
Edit: Didn't realized Chris was also talking about asm configs.
I bring in for example 10 40cm cabinets and create a configuration for each one in the assembly?
The logical thing for me would be editing the instance. There's no such concept in Onshape? Or is that what I'm really going?;)
Seems like lots of part studios.
This is the right way to do it, to have small variations to each cabinet, like here, I make a hole in one.
1. Made a derived part studio
2. Inserted the part into the assembly
3. Edited the part in context
I guess this is the way to do it, to every cabinet here?
It just seems like there should be an easier way;)
This does seem like a problem that could be solved well with a custom feature to produce the base cabinets and set some variables. I imagine a single feature could be made to produce all of the cabinets from a floor plan sketch, then you could just manually modify the ones you need to.
If you want to keep them in separate studios, then yes, what you're doing by deriving them seems like the way to do it. You could do it by configurations, but the more one-off variations you have of the cabinet, the more of your feature tree will be cluttered up with features that are suppressed most of the time. Especially if you want to use the same master across projects, constantly accumulating cabinet variations. Overconfiguring is something I'm prone to do and it gets unwieldy. You could use Super Derive to pull variables (like height and material thickness) from the master model too.
Here's the derived drawer modified in context. Seems following this approach, I'll end up with hundreds of part studios.