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.
Best Of
Re: Free Users in a company
I believe a company should be able to contain a sub-set of free users, for example to share assembly instructions with the shop floor.bradley_sauln said:A Public Onshape account can't be added to a Company at this time. A Company in Onshape allows for Professional users to have centralized billing, ownership, and properties.
If these users show up in the subscription page then it'd be easy to activate a subscription for any such user that might wish to do some design work...
Owen S.
Re: The voting system is non anonymous and biased
To clear up the confusion here:
@rune_thorsen229
Voting is anonymous. You received an email because Owen saw he had a downvote and commented on your thread with the text "Curious about the downvote". You received that email because someone commented on the thread that you started, not because Owen was sending you some message specifically. The email was just pointing out that your thread had a new comment on it.
@rune_thorsen229
Voting is anonymous. You received an email because Owen saw he had a downvote and commented on your thread with the text "Curious about the downvote". You received that email because someone commented on the thread that you started, not because Owen was sending you some message specifically. The email was just pointing out that your thread had a new comment on it.
Re: Does "Copy Workspace" increase speed of large assemblies ?
No it will not affect the performance.
lana
5
Re: Sending a message to the owner
FYI for everyone posting links in this thread, the `/e/aa112233bb4455` portion identifies the tab, so once you copy and paste that, everone who clicks it is always going to go to the tab you were currently on when you copied the URL. If you just go to say:
https://cad.onshape.com/documents/ea73831031c68a9ca068365e
The system will have to infer a tab for you.
So if you ever click a link with /e/ in it, the tab has already been chosen for you.
https://cad.onshape.com/documents/ea73831031c68a9ca068365e
The system will have to infer a tab for you.
So if you ever click a link with /e/ in it, the tab has already been chosen for you.
Feedback for the new browser icon
Part of maintaining the Onshape image is the first impression. The browser icon is the first thing users see. It was modern and simple. Now it is dark, too small, and looks out of date by 10 years.
For a better first impression on users, consider switching to the previous Onshape browser icon.
Current out of date Icon:
The previous better looking browser icon:
For a better first impression on users, consider switching to the previous Onshape browser icon.
Current out of date Icon:
The previous better looking browser icon:
Re: Sending a message to the owner
^ what Owen said. By default, the first tab is the one that is displayed when first opened, so if you put a PDF there, everyone will see it (Feature Studios do not display on mobile). You can also add information to the Document properties (in hamburger menu top left) that will display in the Document info panel on the Documents page, but that is not as obvious,
Re: Sending a message to the owner
Unfortunately, there is no way to do that - it would definitely be useful for collaboration. Content in Public documents is public domain so you don't need the owner's permission to use it. However, we have no control over what content is being uploaded and whether it is infringing somebody else's copyright.
Re: Help rotating text in FeatureScript
Why do you need it to be one sketch operation? Looking again at your case, if you want simple code I really would suggest simply making a new sketch for each entity. The overhead making each sketch is quite small (which you can verify with the FeatureScript profiler).
This change would just mean replacing each of your current calls to skText with something more like:
This change would just mean replacing each of your current calls to skText with something more like:
const angle = 30 * degree;
const textCoordinateSystem = coordSystem(WORLD_ORIGIN, vector(cos(angle), sin(angle), 0), Z_DIRECTION);
var sketch1 = newSketchOnPlane(context, id + i + "sketch", {
"sketchPlane" : plane(textCoordinateSystem)
});
skText(sketch1, "textId", {
"text" : "dtext",
"fontName" : "RobotoSlab-Regular.ttf",
"firstCorner" : vector(x, y) * inch,
"secondCorner" : vector(x+1, y+1) * inch
});
skSolve(sketch1);
</code>const angle = 30 * degree;
var sketch1 = newSketchOnPlane(context, id + i + "sketch", {
"sketchPlane" : plane(WORLD_COORD_SYSTEM)
});
skText(sketch1, "textId", {
"text" : "dtext",
"fontName" : "RobotoSlab-Regular.ttf",
"firstCorner" : vector(x, y) * inch,
"secondCorner" : vector(x+1, y+1) * inch
});
skSolve(sketch1);
opTransform(context, id + i + "transform", {
"bodies" : qCreatedBy(id + "sketch1", EntityType.BODY),
"transform" : rotationAround(Z_AXIS, angle)
});
</pre><div>Completely equivalently, you could avoid calling opTransform entirely by setting the correct coordinate system to on each sketch to begin with:</div><pre class="CodeBlock"><code>Both solutions keep the placement logic for each hole in one place instead of two.
