feat(ui)!: user-created tag colors #801
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CyanVoxel
added
Type: Enhancement
The secondary color now acts as only the text color by default, with the new `color_border` bool serving to optionally restore the previous text + colored border behavior.
CyanVoxel
added
TagStudio: Library
CyanVoxel
changed the title
Add "burgundy", "dark-teal", and "dark_lavender" tag colors.
CyanVoxel
added
Status: Mergeable
csponge
pushed a commit
to csponge/TagStudio
that referenced
this pull request
Mar 10, 2025
* feat: custom tag colors * ui: minor ui polish * ui: add confirmation for deleting colors * ui: match tag_color_preview focused style * ui: reduce spacing between color swatch groups * ui!: change default behavior of secondary color The secondary color now acts as only the text color by default, with the new `color_border` bool serving to optionally restore the previous text + colored border behavior. * ui: adjust focused tag/color button styles * fix: avoid namespace collision * fix: make reserved namespace check case-insensitive * ui: add namespace description + prompt * fix: don't reset tag color if none are chosen * refactor(ui): use form layout for build_color * fix(ui): dynamically scale field title widget * feat(ui): add additional tag shade colors Add "burgundy", "dark-teal", and "dark_lavender" tag colors. * fix: don't check for self in collision checks * fix: update tag references on color update * fix(ui): stop fields widgets expanding indefinitely
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the ability for users to create custom tag colors and groups (namespaces). Tag colors consist of a name, a primary color, and an optional secondary color for borders and text.
This PR also adds three new shade colors: Burgundy, Dark Teal, and Dark Lavender.
Creating Colors
In order to create custom colors, you must first create a new namespace group:
From there, click the "+" button in the new namespace section to create new colors!
Tag colors are created and edited within the new "Manage Tag Colors" window. While built-in colors are immutable, users can create and manage new colors by clicking the "New Namespace" button.
Database Changes
This PR adds an additional column to the
tag_colorstable and thus bumps theDB_VERSIONto 8. Libraries created with this version of TagStudio can still be opened in any existing v9.5.0 pre-release version, however the behavior of custom color borders will not be identical to the behavior in this PR. Otherwise it should still be possible to use any custom colors created in this version in those earlier pre-releases.Closes #264