You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As noted on the Zemax forum, an error is currently raised when trying to use OpticStudioSystem.Save after connecting as extension. In this specific case, the private property _OpenFile is kept as None.
I can see two ways to fix this:
Set the _OpenFile property directly after connecting as extension
Dropping the 'OpenFile' attribute all together and directly checking OpticStudioSystem.SystemFile. As this is a private property, I would not directly consider it a breaking change.
It might be good to address this when addressing #34
The text was updated successfully, but these errors were encountered:
I am currently looking into this and am not sure how to handle it.
is my preferred option, which can be implemented when we introduce the new connection methods.
doesn't seem to be necessary, because OpticStudioSystem.SystemFile is always set (to e.g. <Zemax SAMPLES directory>/Lens.zmx). We can choose to drop the attribute and perform no checks at all.
It is also possible to issue a warning if _OpenFile is None, but still save the file.
As noted on the Zemax forum, an error is currently raised when trying to use
OpticStudioSystem.Save
after connecting as extension. In this specific case, the private property_OpenFile
is kept as None.I can see two ways to fix this:
OpticStudioSystem.SystemFile
. As this is a private property, I would not directly consider it a breaking change.It might be good to address this when addressing #34
The text was updated successfully, but these errors were encountered: