Hi BezierSpline,
I'm reposting an answer here from our closed support forum where we were looking into this with you, so that the open community can also learn from the answers - hope that's OK.
Here the suggestions:
In the case of the vizinput.fileOpen dialog not even being displayed, do you know if the function ever returns from the call or is it essentially freezing the app?
We are not aware of any Windows log files that can shed light on internal OS call failures. However, we've used "Process Monitor" in the past to debug why certain OS calls were failing. Here is a link to download it:
https://docs.microsoft.com/en-us/sys...nloads/procmon
It will display all OS file/registry calls being made by all processes and display whether the call was successful or not. You will need to apply a filter so it only displays calls made by your process. When you display the directory/fileOpen dialogs, you should see a bunch of file/registry calls being made to load thumbnails, folder views, shell extensions, and so on. Hopefully this will help, and it could possibly point to the cause of the problem. In the case of the fileOpen dialog not being displayed, it could at least indicate whether the failure is due to the Python module never actually launching the dialog or if it failed within the OS level after the call was made.
all the best,
The Worldviz team