RE: [PyMOL] stop an accidental or problematic ray trace

[DeLano, W. <wa...@su...>]

Anthony,

I agree that we need one, but it doesn't currently exist.  The same can =
be said for surface calculations, especially when you've loaded a 500 =
frame MD trajectory and accidentally "show surface" (doh!).

My advice: save sessions often and make liberal use of PyMOL's logging =
capability.  When you goof up, kill the process and then reopen the =
session or resume the log file after editing out the offending =
command(s).

Cheers,
Warren

(Hmm...A save session button might be nice...)
--
mailto:wa...@su...
Warren L. DeLano, Ph.D.=20
Informatics Manager=20
Sunesis Pharmaceuticals, Inc.=20
341 Oyster Point Blvd.=20
S. San Francisco, CA 94080=20
(650)-266-3606 FAX:(650)-266-3501



> -----Original Message-----
> From: Anthony Duff [mailto:A....@st...]
> Sent: Tuesday, January 28, 2003 4:29 PM
> To: pym...@li...
> Subject: [PyMOL] stop an accidental or problematic ray trace
>=20
>=20
>=20
>=20
>=20
> It would be nice if there were a button to stop a ray trace,=20
> for when it is=20
> started accidentally, or if something is wrong and it is=20
> taking too long.
>=20
>=20
> Is there one?
>=20
>=20
>=20
>=20
> ----------------------------------------------------------------------
> Anthony Duff
> Postdoctoral Fellow
> School of Molecular and Microbial Biosciences
> Biochemistry Building, G08
> University of Sydney, NSW 2006 Australia
> Phone. 61-2-9351-7817   Fax. 61-2-9351-4726
> ----------------------------------------------------------------------
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> PyMOL-users mailing list
> PyM...@li...
> https://lists.sourceforge.net/lists/listinfo/pymol-users
>=20