Opened 8 years ago
Last modified 8 years ago
#792 assigned enhancement
RFE: add labels (3D) to color/transparency command targets
Reported by: | Elaine Meng | Owned by: | Tom Goddard |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Depiction | Version: | |
Keywords: | Cc: | Greg Couch | |
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
Consider adding a (3D) labels target to the color and transparency commands. I’m neutral as to whether labels should be in the default target, or whether when one specifies a label-model number directly, ChimeraX should know that labels are the target.
Change History (5)
comment:1 by , 8 years ago
Priority: | major → minor |
---|
comment:2 by , 8 years ago
Cc: | added |
---|
Note "color" already includes labels in the default target (i.e. if no target specified, labels get colored too). The "color" command just doesn't allow limiting coloring to labels unless a label model number is specified. I.e. "color orange" will color everything orange, including labels, and "color #1.2 green" will make the label model #1.2 green. So the message to the Log "Label colors not supported yet" from commands like "color pink labels" or "color pink targ l" is misleading. (Obviously, the "label" command can color labels as well.)
comment:3 by , 8 years ago
The "transparency" command accepts "labels" or "target l" without complaint, but it doesn't change their transparency even if a label model number is specified.
Changing label color with "color #1.2 green" or "label color red" does not update the color well shown in the Models list.
Maybe these are separate bugs.
follow-up: 4 comment:4 by , 8 years ago
The bugs are related. The code for parsing the targets and what arguments was unified.
I agree this is worth adding. I expect it to be a while before getting to this.