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.
Fail to publish feature, missing description from exported/imported feature
stuart_robinson
Member Posts: 37 ✭✭
i'm trying to publish this feature Variable Surface Text to add variable text to parts. i found one that looked like it used to work so i took it as an featurescript exercise for myself and tweaked it so it works great for me now. it's using "export import(...)" a feature called Surface Text
but it wont let me publish because Surface Text doesn't have a description
removing the export doesn't work
i'm guessing this description annotation is a new requirement? can i give a description to an imported feature? or anything else i can do to publish?
i dont really understand why it has to be exported for me to use the enum parameter
but it wont let me publish because Surface Text doesn't have a description
removing the export doesn't work
i'm guessing this description annotation is a new requirement? can i give a description to an imported feature? or anything else i can do to publish?
i dont really understand why it has to be exported for me to use the enum parameter
0
Comments
Do you actually need the separate value field? There are two options: you can right-click the string value field and convert it to an expression (like so: https://cad.onshape.com/documents/6dc4aecb038b8172e477a56b/w/93c85c5575b30feaaa16cfeb/e/f81e27b471d56bd846e08fae ), and evidently the Surface Text feature has a "Text is Expression" option.
@jelte_steur814 if i'm understanding you correctly, i think that wouldn't work here because i dont have access to the code for the feature in question