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
What steps will reproduce the problem? 1. run attached file using "python trepHelloWorld.py" What is the expected output? What do you see instead? File should produce two identical, empty trep 3D visualization windows. Instead, after the destruction of first window, there are many GTK warnings printed to terminal, and the second window ends up being decorated with GTK instead of Qt. This ends up producing segmentation faults when running simulations with multiple visualizations in IPython (although they can be worked around by passing "--gui=qt" to IPython invocation).
Beyond IPython issues, one expects all visualization windows to be rendered identically. Please use labels and text to provide additional information.
From [email protected] on June 07, 2013 12:03:04
What steps will reproduce the problem? 1. run attached file using "python trepHelloWorld.py" What is the expected output? What do you see instead? File should produce two identical, empty trep 3D visualization windows. Instead, after the destruction of first window, there are many GTK warnings printed to terminal, and the second window ends up being decorated with GTK instead of Qt. This ends up producing segmentation faults when running simulations with multiple visualizations in IPython (although they can be worked around by passing "--gui=qt" to IPython invocation).
Beyond IPython issues, one expects all visualization windows to be rendered identically. Please use labels and text to provide additional information.
Attachment: trepHelloWorld.py
Original issue: http://code.google.com/p/trep/issues/detail?id=20
The text was updated successfully, but these errors were encountered: