Paul:

It appears to me that you have provided the Python rather than the Scheme 
version of this command, at least based on the use of underscores rather than 
dashes and the fact that the entire command is not in parentheses as opposed to 
just the parameter.  Are you switching entirely to Python?  [No problem from my 
end, just curious.]  Or was this an oversight?  Would the Scheme version be:

(set-nomenclature-errors-on-read "ignore") ?

Also, I have noticed when reading certain RCSB/PDB files that the Fix 
Nomenclature Errors pop-up often questions a few residues.  I thought the RCSB 
(and associated centers) fixed these sorts of errors, so I am concerned about 
why COOT picks up occasional residues as having nomenclature errors.  Any 
thoughts?

Steven

>-----Original Message-----
>From: Mailing list for users of COOT Crystallographic Software
>[mailto:[email protected]] On Behalf Of Paul Emsley
>Sent: Monday, March 05, 2012 9:53 AM
>To: [email protected]
>Subject: Re: Version 7 not repainting screen after initial load.
>
>On 05/03/12 13:56, Ian Tickle wrote:
>> Hello, I just installed WinCoot_0.7-pre-1-4040 (because I kept getting
>> the message "this is an old Coot" from version 0.6.2.1 !).
>
>Sorry about that.  We're just slower at making released that I thought
>we'd be.
>
>I am considering a dynamic check, rather than this built-in
>pre-calculated date...
>
>Anyway...
>
>> I just spotted one minor infelicity: when it starts it pops up a
>> window "Fix Nomenclature Errors" (which is very nice).  However if I
>> close this it still remains visible but inactive.  The same thing
>> happens if I open other dialogs, so eventually I can cover the screen
>> with inactive dialogs!  So it looks like it's not repainting the main
>> window when the dialog window is closed.  This didn't happen with v6.
>> I can however force a repaint by minimising and maximising the window,
>> and after that the dialog windows behave normally.
>
>Sounds like a driver bug.  Although why it should be different for
>different coot versions, I do not know.
>
>> Also is there a
>> way to disable the initial "Fix Nomenclature Errors" pop-up (couldn't
>> see anything in the manual).  I don't want to fix them right away
>> (because it's not my structure), and it keeps reminding me every time!
>
>set_nomenclature_errors_on_read("ignore")
>
>I will add this to the main documentation - thanks for the reminder.
>
>Paul.

This message (including any attachments) may contain confidential, proprietary, 
privileged and/or private information.  The information is intended to be for 
the use of the individual or entity designated above.  If you are not the 
intended recipient of this message, please notify the sender immediately, and 
delete the message and any attachments.  Any disclosure, reproduction, 
distribution or other use of this message or any attachments by an individual 
or entity other than the intended recipient is prohibited.

Reply via email to