Opened 7 years ago
Closed 7 years ago
#1882 closed enhancement (fixed)
Show errors that occur before main window started in GUI log
Reported by: | Tom Goddard | Owned by: | Greg Couch |
---|---|---|---|
Priority: | moderate | Milestone: | |
Component: | UI | Version: | |
Keywords: | Cc: | Eric Pettersen | |
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
When an error occurs before the main window is shown the error goes to the shell, stderr. But on macOS or Windows this error is then never seen. It would be desirable to send the error to stderr but also remember it and if the ChimeraX GUI starts also show it in the GUI log panel.
At last weeks 3d microscopy tutorial, 1/4 of participants got blank graphics when opening any model. There were no errors. Later testing showed that at startup a resize event caused rendering before opengl was setup giving an error and disabling graphics. That error only went to the shell. This would have been trivial to debug if the startup error had been remembered and put into the GUI log panel.
Change History (3)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
In order to generate the error that motivated this bug report change the line in ui/graphics.py resizeEvent()
if self.is_drawable:
to
if self.is_drawable or True:
Then start ChimeraX and you will get the following error to the terminal, but not in the Log panel.
BUG: An error occurred in drawing the scene. Redrawing graphics is now stopped to avoid a continuous stream of error messages. To restart graphics use the command "graphics restart" after changing the settings that caused the error.
Traceback (most recent call last):
File "/Users/goddard/ucsf/chimerax/ChimeraX.app/Contents/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/chimerax/core/updateloop.py", line 69, in draw_new_frame
if ((session.ui.is_gui and session.ui.main_window.graphics_window.is_drawable)
AttributeError: 'UI' object has no attribute 'main_window'
comment:3 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Collations logs don't normally collate bugs (allowing them to immediately get reported), but the early collation log needs to.
Early startup errors *are* shown in the log when it appears. We need to figure out why these particular errors don't.
--Eric