Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Epic Link:
Description
While testing today I noticed that the “Color by…” takes precedence over foreground color. What I mean is that if you use the “Color by…” feature to change the color but later try to change the foreground color of a track, nothing happens.
I think quick and easy customization is key for IGB users and if they choose to change the foreground color I think that action should always be respected, regardless of how they previously chose to customize the color.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-440 [ 15498 ] |
| Rank | Ranked lower |
| Rank | Ranked lower |
| Resolution | Done [ 10000 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 15662 ] | Fall 2019 Workflow Update [ 19353 ] |
| Workflow | Fall 2019 Workflow Update [ 19353 ] | Revised Fall 2019 Workflow Update [ 21470 ] |
The "Color by" setting works similarly to how coloring by strand functions. If a you change the foreground color while using the "Color by" mode, then the foreground color associated with the track should change, but this should not affect the track appearance until the user has deactivated the "Color by" mode by choosing "Color By: None"