Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BUG: Fix reading of default markup active color #6736

Merged
merged 1 commit into from Dec 22, 2022
Merged

BUG: Fix reading of default markup active color #6736

merged 1 commit into from Dec 22, 2022

Conversation

lassoan
Copy link
Contributor

@lassoan lassoan commented Dec 14, 2022

@lassoan lassoan added this to the Slicer 5.3 milestone Dec 14, 2022
@lassoan lassoan self-assigned this Dec 14, 2022
jamesobutler
jamesobutler approved these changes Dec 22, 2022
View reviewed changes
Copy link
Contributor

@jamesobutler jamesobutler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have confirmed through testing that this fixes the issue.

@jamesobutler jamesobutler merged commit cf5a6d3 into main Dec 22, 2022
@jamesobutler jamesobutler deleted the lassoan-fix-markup-active-color branch December 22, 2022 21:22
@jcfr jcfr mentioned this pull request Jan 23, 2023
Merged
@jcfr jcfr modified the milestones: Slicer 5.3, Slicer 5.2.2 Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jamesobutler jamesobutler jamesobutler approved these changes

Assignees

@lassoan lassoan

Labels
None yet
Milestone
Slicer 5.2.2
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@lassoan @jamesobutler @jcfr