Suggestion: New object types that don't use up the comment field

  • 4 May 2020
  • 1 reply
  • 32 views

The comment field is useful not just for the optical designer, but also useful from a product management perspective. I would like to be able to use the comment field to keep track of our internal component part numbering. It is easy to extract this information afterwards using either ZOS-API or just parsing the ZMX file.


 


However, certain object types use the comment field as a data input (Boolean types, CAD types). I understand these cannot be modified for backwards compatibility. Can new Boolean 2 and CAD 2 types be added that move the boolean operation or CAD file path into a parameter?


 


There are work arounds, but having a standard and obvious way to doing things (placing comments in the comment field) is significantly more maintainable.


1 reply

Userlevel 5
Badge +1

Hi Dietrich,


Thanks for your feedback here! I've passed your thoughts on to our Product Team as a feature request. I should note that this isn't a guarantee that the objects as you've mentioned here will be implemented in a future release -- rather, they are weighed based on the impact to the userbase, the difficulty to implement, and the number of users who request it. Still, we appreciate the perspective of our users, as it helps us better understand their needs and workflows going forward.


Please let us know if you have any more questions!


~ Angel

Reply