Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipzCaptureWindow returning incorrect window #77

Open
robmarkcole opened this issue Jul 21, 2017 · 2 comments
Open

ipzCaptureWindow returning incorrect window #77

robmarkcole opened this issue Jul 21, 2017 · 2 comments

Comments

@robmarkcole
Copy link

See below:

image

@indranilsinharoy
Copy link
Collaborator

indranilsinharoy commented Jul 21, 2017

I think this issue is related (or exactly the same as) the issue #74.

But thanks to your images (from which I got to know what version of Zemax/OpticStudio you are using) which gave me a clue. I think I know what the problem is (and perhaps you could also verify).

Just a little background:
The function ipzCaptureWindow() internally uses the function zGetMetaFile() to get an image of the specified analysis window from Zemax, converts it in a png image and displays it.

When Zemax introduced the modern OpticStudio (version 14.0 onward I think), they decided to deprecate few data-items including GetMetaFile. Therefore, technically, in OpticStuido version 14.0 and above it is not even possible to use the ipzCaptureWindow().

Present problem:
It seems to me that in the latest (or some release down the line), it became possible (either by some error in Zemax's side) to call the dataitem GetMetaFile without an error. Furthermore, in my tests I found out that OpticStudio is outputting the layout window irrespective of the analysis code.
Therefore this is a really a bug in OpticStudio and not in PyZDDE.

I also tested in older Zemax (version 13), and the functions--ipzCaptureWindow() and zGetMetaFile() work as expected.

I guess that we will need to report to Zemax for this problem.

@robmarkcole
Copy link
Author

Happy to perform any additional tests you propose.
I agree this is likely a problem for Zemax to resolve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants