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.
Passing and getting additional data to/from manipulator change and editing logic functions
konstantin_shiriazdanov
Member Posts: 1,221 ✭✭✭✭✭
Though manipulator change function takes user constructed manipulator from some intermediate moment of feature evaluation (which internally is a map container) there seem to have been done some specific restrictions to clear any other fields included in manipulator argument map besides of the standard fields. On par with this editing logic and manipulator change functions throw error if you trying to add new field in returned definition with some value calculated inside it to avoid of duplicating some calculations. You can say that these restrictions are made for avoiding some unwanted looping feedback, but if one is persistent enough he can encode, decode and cache data in hidden definition field of isAnything() type, or even in any numeric field of definition directly writing and reading number as bytes. So from this point this looping safety is already compromised, and wish I had a more direct way to pass some neccesary data via definition and manipulator arguments from and to editing logic and manipulator change functions without using dirty hacks like above. Any thoughts?
0