Thaks to Pshemak Maslak for a hint. As usual, simply asking a question focuses wonderfully. So to summarise:
If generating an MO from a cube, then something along the lines of isosurface MO cutoff @x sign blue red "HHa_mo15.cub"; will generate jvxl with these colours. The simplest way I have found of changing the colours AFTER the jvxl has been generated (which is what my original question posed) is to transpose the colours in the two lines of the jvxl file itself. colorNegative="[xffff00]" colorPositive="[xffa500]" I have not yet worked out how to do this in the script line (might it be that the declaration in the jvxl file itself always takes precedence anyway. Perhaps that is what has confused me?) All this applies to Jmol 12.2. One of the problems I have is tracking which feature was introduced when. Thus I cannot vouch how much of this works in eg Jmol 12.1, or 12.0 or earlier. jvxl itself has reached version 2.2. I wonder if some kind soul could document the changes in jvxl, and which versions of jmol support what? Oh, by the way, jvxl is now a fully fledged XML file, with declared namespaces and all sorts of wonderful things. Thanks Bob!! ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
