View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005815 | CaseTalk Modeler | User Interface | public | 2026-07-28 12:25 | 2026-07-28 12:27 |
| Reporter | Marco Wobben | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | 15.0 | Fixed in Version | 15.0 | ||
| Summary | 0005815: Custom colors can be given a name | ||||
| Description | The sixteen custom colors that can be defined for a model are only identifiable by their color. There is no way to record what a color stands for, so the meaning of a color scheme has to be remembered or documented outside the tool, and a diagram gives its reader no clue what its colors signify. Colors can now be given a name. Names are entered in the color list under Preferences, where a color can also be renamed and recolored in place. Named colors are offered wherever a color is picked, so a color can be chosen by its meaning rather than by its appearance. A project can carry a color scheme of its own. It starts from the colors of the tool and, once defined, takes precedence over them, so every model can have its own vocabulary of colors while the preferences keep serving the projects that do not need one. The diagram legend lists the named colors that the diagram actually uses, which makes a diagram with colored containers or concepts readable on its own. Colors without a name are left out. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | Corporate | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-28 12:25 | Marco Wobben | New Issue | |
| 2026-07-28 12:26 | Marco Wobben | Fixed in Version | => 15.0 |
| 2026-07-28 12:26 | Marco Wobben | Target Version | => 15.0 |
| 2026-07-28 12:26 | Marco Wobben | Status | new => resolved |
| 2026-07-28 12:26 | Marco Wobben | Resolution | open => fixed |
| 2026-07-28 12:27 | Marco Wobben | Note Added: 0008684 |