[Jmol-developers] [ jmol-Bugs-1290652 ] omnibus color request (5 issues)

[SourceForge.net <no...@so...>]

Bugs item #1290652, was opened at 2005-09-13 23:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=379133&aid=1290652&group_id=23629

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Scripting
Group: v10.00
Status: Open
Resolution: None
Priority: 5
Submitted By: Bob Hanson (hansonr)
Assigned to: Miguel (migueljmol)
Summary: omnibus color request  (5 issues)

Initial Comment:
1) the command

background hover red

does not work the first time if executed as part of a
script after
load foo.xyz

2) the only two commands that involve color setting
include '
background and color. I suggest we deprecate background
and introduce:

color windowBackground <RGBcolor>
color hoverBackground <the way atoms can color>
color labelBackground <the way atoms can color>
color hover <the way atoms can color>
color labels <the way atoms can color>

so that ALL coloration operates through the color command. 

3) As noted in these suggestions, I suggest that
hoverBackground, labelBackground, hover, and labels
color all be associated with selected atoms, not
globally as they are now. I could imagine using the
hover background, for example, to visually indicate the
chain. As in, perhaps:

color hoverBackground chain

Or the same in terms of label:

color labels chain

Right now this is not possible. 

4) I suggest deprecating  CPK because that coloring
system is somewhat ambiguous, considering the fact that
there are two independent schemes, "jmol" and "rasmol",
and currently if an element color default value is
changed by the user with

color <element name> <color>

then 

color <element name> CPK

doesn't return to the true CPK color; it returns to the
color the user has specified for that element.. 

Instead, I suggest introducing:

color <element name> JMOL
color <element name> RASMOL

to complement

color <element name> <color>

and

color <object> DEFAULT (instead of NONE)

(meaning return to the specified default for that
element, either JMOL, RASMOL, or the specified color
for that element.)

5) The appropriate place for NONE should be

color labelBackground NONE
color hoverBackground NONE

where "NONE" here really means "none" -- that is, no
background. 

I recommend allowing "NONE" to continue to mean
"DEFAULT" in the case of selected objects and sets of
objects. 

In the case of model objects axes, boundbox, measure,
echo, and unitcell, NONE can continue to mean "BLACK" ,
as setting these to none as "not appearing" makes no sense.


Bob Hanson






----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=379133&aid=1290652&group_id=23629