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: Auto part marking scripts?
Yeah I get the gist of how it happens now. There's an order in which the info is processed, and properties happen after features which is why features can set them, but only if they don't get overwritten later when the properties run. Tables run after the properties do, so it can access them.
I'm just wondering if there's a fundamental reason why it could never change. For example if I have a solid body with an ID of 123xyz, the properties for that part exists somewhere in the database at all times. I imagine the limitation is probably something to do with a priority on repeatable regeneration or something rather than a technical impossibility (sort of like why date/time isn't available in featurescript). You want all features to work the same way every time they run. I'm not sure if that's the reason here or something more fundamental.
@ilya_baran care to enlighten us? Is there a chance custom features will ever be able to read properties (not just in editing/manip logic)?
Re: Notes, The Least Loved Part of Onshape
The flip side of this is that as far as I can tell, there are a bunch of ASME and ISO standard symbols which are not in Unicode. Given all the other crazy stuff that's in Unicode, I don't know why engineers don't get any love here. Of course this is a bigger problem, but you'd think that PTC might be big enough to dedicate some resources to influencing solutions to this.
S1mon
Re: Variables and Expressions Lesson
Sorry for the trouble, it does appear that we have a regression. I recommend filing a support ticket so that you know when it's fixed.
_anton
Re: Use Report, viz(), and dbg() for conditional println and debug visualizations
@S1mon Will add. In the meantime use this:
export function viz(context is Context, key is string, start is Vector, end is Vector, color is DebugColor)
where start and end are position vectors in 3space.
jnewth
Re: New Feature: Better Than Boolean
I think I implemented the body ID resolution in a goofy way at the time because there was some issue with editing logic holding the definition correctly where it all worked out if the inputs and references didn't change, but never tested on cases with configurations. I should probably come back and take a look at it with fresh eyes.
Re: 📸 RenderCAD (One-Click Photorealistic Renders!)
@MichaelPascoe That's good news. I did not have much rendering needs in the past weeks, but I'll give it another spin ocne the current job nears completion.
Re: Use Report, viz(), and dbg() for conditional println and debug visualizations
I've just discovered that viz() is missing support for lines. It only wants to draw lines with arrows. 🙁
S1mon
Re: Function variables
I highly recommend watching this video from @EvanReese and the others in the series:
S1mon
Re: Auto part marking scripts?
Depending on what your goals are, I would also recommend implementing QR code or Datamatrix for machine readability.
@jnewth I really wish this kind of thing with part attributes was easier.
S1mon