Vitaly, Great, glad to hear it. Most PyMOL settings now work on a "per object" basis. For example,
set color, red, objectName set sphere_scale, 0.71, solvent set state, 4, objectName Cheers, -- Jason On Tue, Apr 13, 2010 at 4:00 PM, Vitaly Vostrikov <vvos...@uark.edu> wrote: > Jason, > > Thank you very much - it worked perfectly! I did not realize it is possible > to apply that for individual objects. > > Vitaly > > > ----- Original Message ----- > From: Jason Vertrees <jason.vertr...@schrodinger.com> > Date: Tuesday, April 13, 2010 1:58 pm > Subject: Re: [PyMOL] Label size in different scenes > To: Vitaly Vostrikov <vvos...@uark.edu> > Cc: pymol-users@lists.sourceforge.net > >> Vitaly, >> >> You can set label_size per object: >> >> set label_size, -0.35, pseudo1 >> set label_size, -0.50, pseudo2 >> >> I recently ran into similar issues. My solution was to make use of >> the mdo command. Try "help mdo" and check out the PyMOLWiki page >> http://www.pymolwiki.org/index.php/Mdo. >> >> Cheers, >> >> -- Jason >> >> On Tue, Apr 13, 2010 at 12:42 PM, Vitaly Vostrikov >> <vvos...@uark.edu> wrote: >> > Hello, >> > >> > I am learning movie-making in Pymol, and I have a question about >> label size. >> > >> > I have a script with one state and several scenes, and I would >> like to introduce titles for each scene. I create pseudoatoms for >> each scene and label them, but because of the different length of >> text, I would like to have different font size. I thought I could >> do this just by moving pseudoatom further away, but the font size >> in the labels seems to be the "final" size that you see on the >> screen, no matter where a pseudoatom is located. Also, if I >> understand correctly, it is not possible to use the "set >> label_size" command for every scene, as the latest executed one >> will override the previous ones. >> > >> > Is there a workaround for this one? >> > >> > Thank you, >> > Vitaly >> > >> > ------------------------------------------------------------------ >> ------------ >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net) >> > Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users >> > Archives: http://www.mail-archive.com/pymol- >> us...@lists.sourceforge.net> >> >> >> >> -- >> Jason Vertrees, PhD >> PyMOL Product Manager >> Schrodinger, LLC >> >> (e) jason.vertr...@schrodinger.com >> (o) +1 (603) 374-7120 >> > -- Jason Vertrees, PhD PyMOL Product Manager Schrodinger, LLC (e) jason.vertr...@schrodinger.com (o) +1 (603) 374-7120 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net) Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net