Hi Gerhard, works for me. Note that the "mesh_color" setting will take priority over the object color, so once you set the global setting, the "color" command will have no effect anymore on the mesh.
Try to restore the default: # "default" will take object color set mesh_color, default # clear object settings unset mesh_color, * # test fetch 1ubq, map, type=2fofc, async=0 isomesh m1, map, 1 isomesh m2, map, 2 color blue, m1 color red, m2 Cheers, Thomas On 19 Jan 2015, at 08:58, Gerhard Fischer <gf...@cam.ac.uk> wrote: > Hi, > > since upgrading to 1.7.4.0 (both when compiling manually and installing the > package through Yast on openSUSE 13.2), I can no longer give different > isomeshes (of electron density maps) separate colours. > The only way to change the colour seems to be through changing the global > "mesh_color"-setting, but not through the GUI or the "color"-command. > > Is this a bug, a feature or maybe just something specific to my system? Any > ideas? > > > Best regards, > > Gerhard > > -- > Gerhard Fischer, PhD > Postdoctoral Research Associate > > University of Cambridge > Department of Biochemistry > 80 Tennis Court Road > CB2 1GA Cambridge > United Kingdom -- Thomas Holder PyMOL Principal Developer Schrödinger, Inc. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ 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
