#124 closed enhancement (fixed)
Preference so warnings don't show a dialog
Reported by: | Tom Goddard | Owned by: | Eric Pettersen |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Infrastructure | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | chimera |
Description
Currently warnings that occur when opening a PDB or mmCIF file show a dialog and the user has to press Ok to continue. This is not good when running a batch processing script. Would like to have a command to make warnings go to the log without raising a dialog. There might also be a preference setting for this.
The case I encountered was rendering 100 images of mmCIF file assemblies. On 4aa7.cif I get two warning dialogs:
open mmcif:4aa7
Cannot find consistent set of bond orders for ring system containing atom C3 in residue R82 1454.B
Cannot find consistent set of bond orders for ring system containing atom C3 in residue R82 1454.A
also 4aaw.cif produced a warning dialog
open mmcif:4aaw
Cannot find consistent set of bond orders for ring system containing atom C3 in residue R84 1460.A
I'm running my script on the entire PDB (only 100 files as a test so far) so I can't practically click Ok to all these warnings. The script is not run in nogui mode because it needs to render images. Eric Pettersen suggested Python code could push its own exclusive logger to catch all the warnings. In any case the above capability to suppress dialogs for warnings will be useful.
Change History (4)
comment:1 by , 10 years ago
Status: | new → accepted |
---|
comment:2 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
I added a "warningDialog true|false" option to the log command. Set to false, the warnings just go to the log with no dialog. This has allowed my batch image rendering to proceed. I've encountered about a dozen files that give the bond orders warning out of about 500 files.
comment:3 by , 10 years ago
Literally "warningDialog"? You know we aren't using camel case except for class names, right?
This problem is exacerbated by a bug in the atom typing code (#130)